[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Installation of UBUNTU 22.04.1 on August 15, 2022 STILL HAS THIS BUG. The installation was an upgrade from UBUNTU 20.04 which failed due to other issues with PYTHON. Subsequent clean installs of UBUNTU 22.04.1 constantly caused re- occurances of this bug. It was necessary to UNINSTALL brltty to restore access to my USB->Serial converts. Installation of LINUX MINT 21 in December 2022 did --NOT-- have this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Jammy: Fix Released Status in brltty package in Debian: Confirmed Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer - upgrades from focal/impish to the SRU version should have no question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - upgrades from brltty 6.4-4ubuntu2 1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question 1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated 1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed 2. if no matching device is connected there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - installing brltty when it was not installed no question and no config generated * Regression potential If the debconf logic is wrong users could be prompted with the question when not needed or not prompted when they should. If the udev rules was incorrect or wrongly installed it could lead to have brltty not starting when it should --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990357] Re: ch340 USB/serial - brltty interference
Under UBUNTU 22.04.1 brltty PREVENTED me from using a USB->serial converter to access a remote piece of equipment. Once uninstalled, I had full access to the remote device. Under LINUX MINT 21, you cannot uninstall brltty, and it did --NOT-- create a problem with the remote device, other than a name change to the port. Under UBUNTU 22.04.1, the port is named /dev/ttyUSB0 Under Linux Mint 21, the port is named /dev/ttyS0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990357 Title: ch340 USB/serial - brltty interference Status in brltty package in Ubuntu: Confirmed Bug description: the CH340 does show up in lsusb: 'Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics CH340 serial converter' but does not show up in /dev if brltty is installed on the system. Device does show up as /dev/ttyUSB0 after removing brltty and rebooting. tested systems: Ubuntu 22.04.1 (live USB) - problem present Linux Mint 21 (fresh install, updated) - problem present ubuntu-bug does not recognise brltty as an ubuntu package and thus refuses to collect data. The CH340 is a very common USB/serial converter chip used in cheap 3D printers and microcontroller development boards. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5json: { CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21 InstallationDate: Installed on 2022-09-20 (0 days ago) InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: brltty 6.4-4ubuntu3 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Tags: third-party-packages vanessa Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839544] Re: power setting "display off" maximum is 15 minutes, used to have several hour increment values
This should be a very simple thing to fix. And if I knew "C" I would fix it myself. but I don't, my knowledge base is in many other computer programming languages that date all the way back to the 1960's. While I still program computers, now-a-days they are primarily a tool to be used in solving other problems... In my opinion, the best long term fix would be to provide a "[ ] other" box with a way to allow entering the actual idle time desired -- then a user can set it to what ever their circumstances dictates. unfortunately, The concept of "keyboard idle" is not necessarily the best indication of an "unattended terminal". and the futuristic concept of tracking eyeball movements to see if anybody is actually looking at the screen, would probably not be acceptable to most humans. "15 min" of no keyboard/mouse movement is too short a time period, especially when the screen is being used to display reference material. "never" is too long, especially when you need to keep user specific background processes running - or I would simply logoff and log back on later. (One would hope that the user selectable "idle time" values are being translated internally to some form of seconds or minutes, and that they are not simply used to set a series of "bit switches", thus my suggestion to provide a text entry box.) I would also like to suggest that most folks use a computer to solve real world problems, and that computers exist primarily as a tool to be used, and not just as just programming exercises Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839544 Title: power setting "display off" maximum is 15 minutes, used to have several hour increment values Status in gnome-control-center package in Ubuntu: New Bug description: Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS. In the POWER settings for blanking the display, there used to be several options that allowed selecting a time interval of 1 hour, 2 hours, 4 hours, etc. Under Ubuntu 18.04.2 there are only 9 selectable time values: i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes, and never. This might be fine for a portable laptop running on batteries, but is not acceptable for a desktop system. The never option is not good, because then the monitor NEVER goes dark. My preferred time is to set this to 1-hour because of the length of conference calls. It is a real nuisance to have the screen blank on you while you are reading information displayed on the screen to a multi-person conference call... ...Especially if you lock your screen, requiring you to log back on. I suggest adding some of the time values back to the pull down list, or possibly adding a "other" fill-in value box where the user can specify in minutes when he wants the screen to blank when idle. I consider this to be a bug, and not a feature enhancement, because I used to be able to say "1 hour". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839544] [NEW] power setting "display off" maximum is 15 minutes, used to have several hour increment values
Public bug reported: Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS. In the POWER settings for blanking the display, there used to be several options that allowed selecting a time interval of 1 hour, 2 hours, 4 hours, etc. Under Ubuntu 18.04.2 there are only 9 selectable time values: i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes, and never. This might be fine for a portable laptop running on batteries, but is not acceptable for a desktop system. The never option is not good, because then the monitor NEVER goes dark. My preferred time is to set this to 1-hour because of the length of conference calls. It is a real nuisance to have the screen blank on you while you are reading information displayed on the screen to a multi-person conference call... ...Especially if you lock your screen, requiring you to log back on. I suggest adding some of the time values back to the pull down list, or possibly adding a "other" fill-in value box where the user can specify in minutes when he wants the screen to blank when idle. I consider this to be a bug, and not a feature enhancement, because I used to be able to say "1 hour". ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839544 Title: power setting "display off" maximum is 15 minutes, used to have several hour increment values Status in gnome-control-center package in Ubuntu: New Bug description: Just upgraded to Ubuntu 18.04.2 LTS from Ubuntu 16.04 LTS. In the POWER settings for blanking the display, there used to be several options that allowed selecting a time interval of 1 hour, 2 hours, 4 hours, etc. Under Ubuntu 18.04.2 there are only 9 selectable time values: i.e. 1 min, 2 min, 3 min, 4 min, 5 min, 8 min, 10 min, 12 min, 15 minutes, and never. This might be fine for a portable laptop running on batteries, but is not acceptable for a desktop system. The never option is not good, because then the monitor NEVER goes dark. My preferred time is to set this to 1-hour because of the length of conference calls. It is a real nuisance to have the screen blank on you while you are reading information displayed on the screen to a multi-person conference call... ...Especially if you lock your screen, requiring you to log back on. I suggest adding some of the time values back to the pull down list, or possibly adding a "other" fill-in value box where the user can specify in minutes when he wants the screen to blank when idle. I consider this to be a bug, and not a feature enhancement, because I used to be able to say "1 hour". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320428] Re: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic
** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1320428 Title: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic Status in firefox package in Ubuntu: Fix Released Bug description: Note: attached system information captured under Linux 3.11.0-20-generic. The actual hang occurs under Linux 3.11.0-24-generic. I am assuming the actual bug has to do with this particular combination of Kernal and Firefox. tagged it as kernal, as the same version of firefox works under previous kernal When the SYSTEM hangs, you lose all control. Only a power-switch reboot will recover. Hang NEVER occurs under Linux 3.11.0-20-generic and will ALWAYS hang when firefox is started under Linux 3.11.0-24-generic No differences after reinstalling the -24 system, and/or firefox using Synaptic Package Manager. Can assist in debugging, but am not an "expert" in linux. - - - - My system uses an NVIDIA GeForce 8600GTS video card. ubuntu-drivers-common 1:0.2.91.4 xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 if I boot the system under the recently distributed 3.11.0-24-generic and then start Firefox 29, (also recently distributed) my system will lockup, and I will have to use the power button to reboot. if I boot the 3.11.0-20-generic kernal, then there is no problem. hints anyone? Firefox Release 29 fails (hangs) in this environment: uname -r;lsb_release -a 3.11.0-24-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory: 4GB Firefox Release 29 works in this environment: uname -r;lsb_release -a 3.11.0-20-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory 4GB ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 29.0+build1-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid firewire_ohci forcedeth firewire_core pata_acpi crc_itu_t sata_nv pata_amd floppy AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 BuildID: 20140428193813 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDesktop: Unity Date: Sat May 17 01:41:49 2014 DefaultProfileIncompatibleExtensions: English (GB) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefSources: prefs.js ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-11 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.7.99 dev eth0 proto static 192.168.7.99 dev eth0 proto static scope link IwConfig: eth0 no wireless extensions. lono wireless extensions. MostRecentCrashID: bp-3adbdd30-b995-477d-a458-ff34e2130425 PciNetwork: ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use) Profile1 - LastVersion=23.0/20130803192641 (Out of date) RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: May 16 14:49:33 wb4alm-07 kernel: [146307.851001] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 6.116 msecs dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1401 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1401:bd06/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX: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/firefox/+bug/1320428/+subscriptions -
[Desktop-packages] [Bug 1639201] Re: Can not resize GEDIT windows by moving window edge
I have confirmed that changing the theme fixed the problem in both "gedit" and in "files". I will use Greybird for the time being. Again, thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639201 Title: Can not resize GEDIT windows by moving window edge Status in Ubuntu GNOME: Triaged Status in light-themes package in Ubuntu: Confirmed Bug description: Gedit UBUNTU 16.04.1 GNOME 3-20 GEDIT 3.20.2 Please restore the previously available ability to resize the gedit window by grabbing an edge or corner of the window and moving the edge. I manipulate many text files each day and frequently have several open and visible at the same time on the same monitor. (I have multiple monitors.) The ability to quickly change the dimensions of individual windows is very important, and the "new" GNOME 3 method of: 1. Move mouse to title bar, right click 2. move the "selection" bar -DOWN- several lines, click on the word "resize" 3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand or reduce the window size. 4. More often then NOT, you then get to do this all over again because the computer moved the left side of the window, rather then the right side as you had intended, or the top of the window instead of the bottom, or some sort of vice-versa forcing you to now move your cursor to the top of the screen to reposition the entire window. Much easier to just grab an edge and move THAT edge. I have also noticed that the majority of the applications installed on my system also allow grabbing the window edges, even though most of them also have the "click on a non-existant icon and hope that you get a usable pulldown menu to do something useful." method of selecting options that gnome 3 seems to like. What's worse is where the "help" and "preferences" selections are - especially when you have a multi-monitor sysytem. (But I will have to say, that GNOME 3 is much better than UNITY.) Now if this method of selecting options (Resize, help, preferences, Print, etc) was done to support "Touch screens" then I have to ask, please, PLEASE, provide a user selectable option of "Desktop" or "Touch Screen" so that the user can make their own choice... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 4 06:32:16 2016 InstallationDate: Installed on 2014-05-11 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639201] Re: Can not resize GEDIT windows by moving window edge
Thank YOU, Jeremy for the assistance. Had you not said "different theme" I would not have remembered to look in that direction to see exactly what was being used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639201 Title: Can not resize GEDIT windows by moving window edge Status in Ubuntu GNOME: Triaged Status in light-themes package in Ubuntu: Confirmed Bug description: Gedit UBUNTU 16.04.1 GNOME 3-20 GEDIT 3.20.2 Please restore the previously available ability to resize the gedit window by grabbing an edge or corner of the window and moving the edge. I manipulate many text files each day and frequently have several open and visible at the same time on the same monitor. (I have multiple monitors.) The ability to quickly change the dimensions of individual windows is very important, and the "new" GNOME 3 method of: 1. Move mouse to title bar, right click 2. move the "selection" bar -DOWN- several lines, click on the word "resize" 3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand or reduce the window size. 4. More often then NOT, you then get to do this all over again because the computer moved the left side of the window, rather then the right side as you had intended, or the top of the window instead of the bottom, or some sort of vice-versa forcing you to now move your cursor to the top of the screen to reposition the entire window. Much easier to just grab an edge and move THAT edge. I have also noticed that the majority of the applications installed on my system also allow grabbing the window edges, even though most of them also have the "click on a non-existant icon and hope that you get a usable pulldown menu to do something useful." method of selecting options that gnome 3 seems to like. What's worse is where the "help" and "preferences" selections are - especially when you have a multi-monitor sysytem. (But I will have to say, that GNOME 3 is much better than UNITY.) Now if this method of selecting options (Resize, help, preferences, Print, etc) was done to support "Touch screens" then I have to ask, please, PLEASE, provide a user selectable option of "Desktop" or "Touch Screen" so that the user can make their own choice... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 4 06:32:16 2016 InstallationDate: Installed on 2014-05-11 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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"
While I am only 1 of 2593 people affected by this bug, (and other problems such as screen/system hangs caused by the driver) I have decided to replace my NVIDIA Display card with an older model NVIDA graphics adapter, and have regressed the nvidia-graphics-driver to the 304 version. In the past two weeks I have had ZERO problems, and in the past, I have had as many as three-four screen/system hangs EACH DAY. After posting this comment, I will be unsubscribing to this particular bug, and will be researching other variations of LINUX since UBUNTU is no longer really supporting their LTS model. I wish you all good luck! -- 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: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released 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 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"
Since the fix is known, why not apply it to nvidia-331 and be done with this foolishness? -- 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: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged 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 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"
Not sure about the previous message: >> Daniel van Vugt (vanvugt) 8 hours ago >> Changed in nvidia-graphics-drivers-331 (Ubuntu): >> status: Fix Released → Triaged >> Changed in nvidia-graphics-drivers-331-updates (Ubuntu): >> status: Fix Released → Triaged as the update just applied (01 May 2015 0545 Eastern Time) to my machine failed with the exact same status as it has for a long time. -- 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: Fix Released Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged 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 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 wonder if I'll live long enough to see this bug actually fixed. Since version 340 has it fixed, why can't the fixed be retrofitted to version 331? -- 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: Fix Released 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 1387683] Re: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build (still #10)
"UpgradeStatus: No upgrade log present (probably fresh install)" yes, the installation of 14.04 was a clean new install, and all auto-updates have been applied since then. Does anybody have any suggestions? If this continues I will have to find a better linux distribution. -- 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/1387683 Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build (still #10) Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: I have followed all of the suggestions on removing, re-installing etc. I never have any problems re-installing. but the very next auto- update allways fails with this same error. This is around the 10th time I have had to report this problem, and everytime that it is flagged as a dup of some other problem, I follow those instructions to no avail. Is there ever going to be a fix? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-39-generic Date: Thu Oct 30 09:59:18 2014 InstallationDate: Installed on 2014-05-11 (172 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-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-updates/+bug/1387683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387683] [NEW] nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build (still #10)
Public bug reported: I have followed all of the suggestions on removing, re-installing etc. I never have any problems re-installing. but the very next auto-update allways fails with this same error. This is around the 10th time I have had to report this problem, and everytime that it is flagged as a dup of some other problem, I follow those instructions to no avail. Is there ever going to be a fix? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-39-generic Date: Thu Oct 30 09:59:18 2014 InstallationDate: Installed on 2014-05-11 (172 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (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 nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1387683 Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-uvm kernel module failed to build (still #10) Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: I have followed all of the suggestions on removing, re-installing etc. I never have any problems re-installing. but the very next auto- update allways fails with this same error. This is around the 10th time I have had to report this problem, and everytime that it is flagged as a dup of some other problem, I follow those instructions to no avail. Is there ever going to be a fix? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates-uvm 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-39-generic Date: Thu Oct 30 09:59:18 2014 InstallationDate: Installed on 2014-05-11 (172 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.38-0ubuntu7.1: nvidia-331-updates-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-updates/+bug/1387683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380060] Re: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
Why not re-release the 331 driver with the bug fixed? -- 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/1380060 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: failed again, again. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-37-generic Date: Sat Oct 11 07:30:33 2014 InstallationDate: Installed on 2014-05-11 (153 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1380060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380060] [NEW] nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
Public bug reported: failed again, again. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-37-generic Date: Sat Oct 11 07:30:33 2014 InstallationDate: Installed on 2014-05-11 (153 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (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 nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1380060 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: failed again, again. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 DKMSKernelVersion: 3.13.0-37-generic Date: Sat Oct 11 07:30:33 2014 InstallationDate: Installed on 2014-05-11 (153 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1380060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318252] Re: nvidia-331-updates 331.38-0ubuntu7: nvidia-331-updates kernel module failed to build ["nvidia.ko failed to build!" but no reason why]
Same as usuall - only get message "failed to build module", no other readson given. this has been occuring for MONTHS now. individual install of nvidia 331 always works, and always fails during packaged updated -- 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/1318252 Title: nvidia-331-updates 331.38-0ubuntu7: nvidia-331-updates kernel module failed to build ["nvidia.ko failed to build!" but no reason why] Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: I can't build it with kernel 3.15-rc4 (amd64) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu7 Uname: Linux 3.15.0-eudyptula-00299-g28be335 x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 DKMSKernelVersion: 3.15.0-eudyptula-00299-g28be335 Date: Sat May 10 08:50:38 2014 InstallationDate: Installed on 2013-08-09 (273 days ago) InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130423.1) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu7: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-04-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1318252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 no obvious error [objdump: '... .tmp_nv.o': No such file]
Can't tell if the debug information captured bny my system has been uploaded and/or attached to this report. If you need it, you will have to tell me where to find it on my system, and I'll be glad to manually attach it. -- 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 no obvious error [objdump: '... .tmp_nv.o': No such file] Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Triaged Bug description: 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/ubuntu/+source/nvidia-graphics-drivers-331/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]
This is the fifth (or more) update of the kernel, where i have to manuaaly delete and reinstall the Nvidia 331.38 driver. My card is a geforce 8600... and this problem has been occuring for a long, long time. Most of my past reports have been tag as duplicates of other reported bug, the last three or so were declared to be dups of this report (1268257), so i decided to tag it that way right off... -- 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 no obvious error [objdump: '... .tmp_nv.o': No such file] Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Triaged Bug description: 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/ubuntu/+source/nvidia-graphics-drivers-331/+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 1358457] [NEW] nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
Public bug reported: Please verify that attached data is the same as a previous bug, BEFORE tagging it as a duplicate. Thank You. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-34-generic Date: Mon Aug 18 15:08:58 2014 InstallationDate: Installed on 2014-05-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (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 nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1358457 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Please verify that attached data is the same as a previous bug, BEFORE tagging it as a duplicate. Thank You. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-34-generic Date: Mon Aug 18 15:08:58 2014 InstallationDate: Installed on 2014-05-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1358457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1356485] [NEW] nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
Public bug reported: DO NOT TAG AS A DUPLICATE UNTIL AFTER THE ATTACHED DEBUG INFORMATION HAS BEEN EVALUATED.Thank You. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-33-generic Date: Wed Aug 13 13:03:49 2014 InstallationDate: Installed on 2014-05-11 (94 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (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 nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1356485 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: DO NOT TAG AS A DUPLICATE UNTIL AFTER THE ATTACHED DEBUG INFORMATION HAS BEEN EVALUATED.Thank You. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DKMSKernelVersion: 3.13.0-33-generic Date: Wed Aug 13 13:03:49 2014 InstallationDate: Installed on 2014-05-11 (94 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1356485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1347933] [NEW] nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
Public bug reported: Each individual update reports tis problem, even after nvidia has been installed by itself after the "pakaged updates" ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-32-generic Date: Wed Jul 23 17:18:45 2014 InstallationDate: Installed on 2014-05-11 (73 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (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 nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1347933 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Each individual update reports tis problem, even after nvidia has been installed by itself after the "pakaged updates" ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-32-generic Date: Wed Jul 23 17:18:45 2014 InstallationDate: Installed on 2014-05-11 (73 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1347933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335357] [NEW] nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
Public bug reported: Failed to install when processing list of upgrades ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Fri Jun 27 19:13:24 2014 InstallationDate: Installed on 2014-05-11 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (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 nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1335357 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Failed to install when processing list of upgrades ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Fri Jun 27 19:13:24 2014 InstallationDate: Installed on 2014-05-11 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1335357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325426] Re: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
Do not know what really triggered this problem - was applying latest series of updates including Kernel 3.13.0-29-generic -- 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/1325426 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: driver failed to build when installing linux-image-3.13.0-29-generic (3.13.0-29.52) and friends from the trusty-proposed source ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ I'll attach the build log in case apport didn't do it automatically. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-29-generic Date: Sun Jun 1 16:46:37 2014 PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1325426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320428] Re: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic
uname -r;lsb_release -a 3.13.0-27-generic No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty The problem has gone away with the installation of Linux kernal 3.13.0-27-generic. This record can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1320428 Title: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic Status in “firefox” package in Ubuntu: New Bug description: Note: attached system information captured under Linux 3.11.0-20-generic. The actual hang occurs under Linux 3.11.0-24-generic. I am assuming the actual bug has to do with this particular combination of Kernal and Firefox. tagged it as kernal, as the same version of firefox works under previous kernal When the SYSTEM hangs, you lose all control. Only a power-switch reboot will recover. Hang NEVER occurs under Linux 3.11.0-20-generic and will ALWAYS hang when firefox is started under Linux 3.11.0-24-generic No differences after reinstalling the -24 system, and/or firefox using Synaptic Package Manager. Can assist in debugging, but am not an "expert" in linux. - - - - My system uses an NVIDIA GeForce 8600GTS video card. ubuntu-drivers-common 1:0.2.91.4 xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 if I boot the system under the recently distributed 3.11.0-24-generic and then start Firefox 29, (also recently distributed) my system will lockup, and I will have to use the power button to reboot. if I boot the 3.11.0-20-generic kernal, then there is no problem. hints anyone? Firefox Release 29 fails (hangs) in this environment: uname -r;lsb_release -a 3.11.0-24-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory: 4GB Firefox Release 29 works in this environment: uname -r;lsb_release -a 3.11.0-20-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory 4GB ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 29.0+build1-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid firewire_ohci forcedeth firewire_core pata_acpi crc_itu_t sata_nv pata_amd floppy AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 BuildID: 20140428193813 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDesktop: Unity Date: Sat May 17 01:41:49 2014 DefaultProfileIncompatibleExtensions: English (GB) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefSources: prefs.js ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-11 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.7.99 dev eth0 proto static 192.168.7.99 dev eth0 proto static scope link IwConfig: eth0 no wireless extensions. lono wireless extensions. MostRecentCrashID: bp-3adbdd30-b995-477d-a458-ff34e2130425 PciNetwork: ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use) Profile1 - LastVersion=23.0/20130803192641 (Out of date) RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: May 16 14:49:33 wb4alm-07 kernel: [146307.851001] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 6.116 msecs dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1401 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1401:bd06/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Produ
[Desktop-packages] [Bug 1320428] Re: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic
Since the attached apport system info was from the Linux 3.11.0-20-generic boot (trusty amd64 apport-bug) how do I provide information on the 3.11.0-24-generic boot? The momment I try to start firefox, the system will hang! Thanks... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1320428 Title: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic Status in “firefox” package in Ubuntu: New Bug description: Note: attached system information captured under Linux 3.11.0-20-generic. The actual hang occurs under Linux 3.11.0-24-generic. I am assuming the actual bug has to do with this particular combination of Kernal and Firefox. tagged it as kernal, as the same version of firefox works under previous kernal When the SYSTEM hangs, you lose all control. Only a power-switch reboot will recover. Hang NEVER occurs under Linux 3.11.0-20-generic and will ALWAYS hang when firefox is started under Linux 3.11.0-24-generic No differences after reinstalling the -24 system, and/or firefox using Synaptic Package Manager. Can assist in debugging, but am not an "expert" in linux. - - - - My system uses an NVIDIA GeForce 8600GTS video card. ubuntu-drivers-common 1:0.2.91.4 xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 if I boot the system under the recently distributed 3.11.0-24-generic and then start Firefox 29, (also recently distributed) my system will lockup, and I will have to use the power button to reboot. if I boot the 3.11.0-20-generic kernal, then there is no problem. hints anyone? Firefox Release 29 fails (hangs) in this environment: uname -r;lsb_release -a 3.11.0-24-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory: 4GB Firefox Release 29 works in this environment: uname -r;lsb_release -a 3.11.0-20-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty memory 4GB ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 29.0+build1-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid firewire_ohci forcedeth firewire_core pata_acpi crc_itu_t sata_nv pata_amd floppy AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 BuildID: 20140428193813 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDesktop: Unity Date: Sat May 17 01:41:49 2014 DefaultProfileIncompatibleExtensions: English (GB) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefSources: prefs.js ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-11 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.7.99 dev eth0 proto static 192.168.7.99 dev eth0 proto static scope link IwConfig: eth0 no wireless extensions. lono wireless extensions. MostRecentCrashID: bp-3adbdd30-b995-477d-a458-ff34e2130425 PciNetwork: ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use) Profile1 - LastVersion=23.0/20130803192641 (Out of date) RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: May 16 14:49:33 wb4alm-07 kernel: [146307.851001] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 6.116 msecs dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1401 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1401:bd06/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Vers
[Desktop-packages] [Bug 1320428] [NEW] Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic
Public bug reported: Note: attached system information captured under Linux 3.11.0-20-generic. The actual hang occurs under Linux 3.11.0-24-generic. I am assuming the actual bug has to do with this particular combination of Kernal and Firefox. tagged it as kernal, as the same version of firefox works under previous kernal When the SYSTEM hangs, you lose all control. Only a power-switch reboot will recover. Hang NEVER occurs under Linux 3.11.0-20-generic and will ALWAYS hang when firefox is started under Linux 3.11.0-24-generic No differences after reinstalling the -24 system, and/or firefox using Synaptic Package Manager. Can assist in debugging, but am not an "expert" in linux. - - - - My system uses an NVIDIA GeForce 8600GTS video card. ubuntu-drivers-common 1:0.2.91.4 xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 if I boot the system under the recently distributed 3.11.0-24-generic and then start Firefox 29, (also recently distributed) my system will lockup, and I will have to use the power button to reboot. if I boot the 3.11.0-20-generic kernal, then there is no problem. hints anyone? Firefox Release 29 fails (hangs) in this environment: uname -r;lsb_release -a 3.11.0-24-generic No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty memory: 4GB Firefox Release 29 works in this environment: uname -r;lsb_release -a 3.11.0-20-generic No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 Codename: trusty memory 4GB ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 29.0+build1-0ubuntu0.14.04.2 ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: hid_generic usbhid hid firewire_ohci forcedeth firewire_core pata_acpi crc_itu_t sata_nv pata_amd floppy AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 BuildID: 20140428193813 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable CurrentDesktop: Unity Date: Sat May 17 01:41:49 2014 DefaultProfileIncompatibleExtensions: English (GB) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefSources: prefs.js ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-11 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.7.99 dev eth0 proto static 192.168.7.99 dev eth0 proto static scope link IwConfig: eth0 no wireless extensions. lono wireless extensions. MostRecentCrashID: bp-3adbdd30-b995-477d-a458-ff34e2130425 PciNetwork: ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use) Profile1 - LastVersion=23.0/20130803192641 (Out of date) RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: May 16 14:49:33 wb4alm-07 kernel: [146307.851001] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) took too long to run: 6.116 msecs dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1401 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1401:bd06/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1320428 Title: Firefox 29 fails (system hang) under Linux 3.11.0-24-generic, works under 3.11.0-20-generic Status in “firefox” package in Ubuntu: New Bug description: Note: attached system information captured under Linux 3.11.0-20-generic. The actual hang occurs under Linux 3.11.0-24-generic. I am assuming the actual bug has to do with this particular combination of Kernal and Firefox. tagged it as kernal, as the same version of firefox
[Desktop-packages] [Bug 1290342] [NEW] Frequent System Hangs
Public bug reported: bill@WB4ALM-07:~$ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 bill@WB4ALM-07:~$apt-cache policy pkgname N: Unable to locate package pkgname I get frequent system hangs... ...sometime xorg restarts itself, many times it does not. Usually I have no keyboard or mouse clicks when it hangs. Sometimes I can move the cursor around the screen, but am unable to click on anything. If I have an active (95 chars by 45 lines) terminal, then it will usually resize the terminal to the default size (80 chars by 24 lines). It does not seem to matter what application software is running. I have seen the problem occur with firefox, system monitor, terminal sessions running REXX scripts, gedit, and th file manager. It does not seem to have an real pattern that I have been able to discover other than "SIGABRT" eventually showing up in various other routines such as GNOME. My display card is a dual display 8600GTS with 512M onboard. I have been using that card since I first started with Ubuntu 8-04 and 10-04 and it worked exceeding well until I upgraded to 12-04 (12-04, 12-10, 13-04, 14-10) When I first instralled the card I was able to support 4 monitors. One monitor on one port and the other three on the second port connected thru a Tripple-togo external adapter from Matrix. the two seperate sets of monitors were run as separate x-windows and I was very, very happy with that setup. under 12-04 and all successor versions, the seprate x-server mechanism has NOT functioned - resulting in my removal of the tripple-to-go adapter and its three monitors from this system. I now only run a single monitor, and am so severly plaged with XORG failures, that I can no longer use this system as part of my Ham Radio setup, as the system is too unstable to use in digital communications. Please note, ALL system failures have been transmitted to UBUNTU for the past four years. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-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 304.88 Wed Mar 27 14:26:46 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Mar 10 08:06:31 2014 DistUpgraded: 2013-10-21 11:14:52,695 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-15-generic, x86_64: installed nvidia-304, 304.88, 3.11.0-17-generic, x86_64: installed nvidia-304, 304.88, 3.11.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GTS] [10de:0400] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:c773] InstallationDate: Installed on 2013-05-04 (310 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=9687e09d-6ef0-45b9-a28c-617031682b72 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-21 (139 days ago) dmi.bios.date: 06/21/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1401 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1401:bd06/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-n
[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites
Like many others, I have been getting random screen freezes since July 2013. They are more frequent under 13.10, but I was also getting them under 13.04 I have a quad processor, and it seems that if one cpu approaches 100%, I am much more likely to see a screen freeze. Some of the freezes clear themselves in a time fram of 15 seconds to a couple of minutes. If more than two of the copu's go to 100% it is highly probably that a Hard reboot (with the power switch) will be required. (Could there be a kernal logic problem in signalling between the cpu's?) When the "unfreeze" occurs, I will see a screen flash and then the screen is rewritten and everything is fine for a while. If the unfreeze does not occur within a few minutes, I have found that a hard reboot with the power switch is necessary. Sometimes when the screen freezes, the cursor can be moved, but button clicks will no longer work, nor will the keyboard. My keyboard and trackball are both USB if that makes a difference, and my VIDEO card is a NVIDIA GeForce 8600 GTS using NVIDIA's 304.88 driver. I have had multiple monitors attached to my system in the past using my dual port card, but in the last 6 months have only had a ViewSonic VA1930wm at 1440x900 pixels. (In fact, prior to ubuntu 10.04, I was able to run them as separate x-screens, but that went away with Ubuntu 10.04) As a radio Amateur, I frequently run a program called FLDIGI to control one of my Radio Transmitters. When I had FLDIGI configured to use portaudio, everything was fine from Ubuntu 8.04 all the way to Ubuntu 10.04. With Ubuntu 10.04 I started to get some freezes using Portaudio and under Ubuntu 12.10 it was totally unusable - so I switched to PulseAudio (as recommended by the FLDIGI author), and as a result the freezes were less frequent until Ubuntu 13.10, when the freezes became quite frequent. I have no way to tell if the problen is X-server related, or if it is pulseAudio related, or if it has to do with signaling within the kernal. Sometimes when the system "fixes" itself, a problem analysis is created and I assume is transmitted to Ubuntu support. I know for a fact that NO report is generated when I have to hard boot the system. If the screen freezes and can not be fixed, then I will have to abandon Ubuntu and go to mint 13 or mint 14 like a lot of other Radio Amateurs have already done. It is just not acceptable when I am in the middle of a radio conversation with other Radio Hams to have the Ubuntu system freeze and cause my radio transmitter to suddenly stop sending data, but continue to transmit a signal, and then go suddenly off the air when the system is rebooted. Not only is it not polite to just disappear, it is a violation of the FCC's rules and regulations to not end the transmission with my call sign. -- 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/1184451 Title: Ubuntu 13.10 random screen freeze while Normal OS activites Status in “xorg-server” package in Ubuntu: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: I have recently, re-installed fresh ubuntu 13.10 distribution release. But everything worked fine. until recently i had strange problem of my display screen getting freezed randomly; but no response to either mouse/keyboard. But i want to point it out; it happens randomly and is not specific ? Other day, i had music player playing in background, but screen freezed. but my music was still running. Kindly note, i used multiple monitor setup and same issue of screen freeze also cropped up. I,am not sure, whether it is bug ? thanks for the expertise support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034156] Re: System Log will not launch
Yes, syslog will start in 13.04, but the time and date stamps are still invisable unless you actually select (highlight) one or more lines. This means that it still is not as usuable as it should be. /s/ Bill Turner, wb4alm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1034156 Title: System Log will not launch Status in “policykit-1” package in Ubuntu: Confirmed Bug description: After updating to quantal my menu entry named System Log will not launch After checking the menu entry properties I saw that the associated command was 'pkexec gnome-system-log'. If I run this command at a terminal window, it will ask for my password and then it shows the gnome-system-log window as is supposed to. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-8-generic 3.5.0-8.8 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorgehsrama 2173 F pulseaudio Date: Tue Aug 7 22:14:04 2012 HibernationDevice: RESUME=UUID=8170e72c-3b1e-48b8-9dd3-f93f30791e6a InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) Lsusb: Bus 001 Device 004: ID 0011:7788 Bus 001 Device 002: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic root=UUID=0a689cc1-8f39-4ff3-8297-878646ffed1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-8-generic N/A linux-backports-modules-3.5.0-8-generic N/A linux-firmware 1.88 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-07-28 (10 days ago) dmi.bios.date: 09/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr218:bd09/21/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1034156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885989] Re: white screen on second monitor when using two xsessions
I agree with Paul, I do not understand why this still has not been fixed. Multiple screen support worked in Ubuntu 10.04 and 10.10, and does not now work in Ubuntu 11.xx or Ubuntu 12.xx (I am currently on Ubuntu 12.10, would have prefered to stay on 12.04 LTS, but other issues with 12.04.1 forced me to upgrade to 12.10) Since I am accustomed to being able to run separate X screens, (one "screen" was a single 1024x768, and the other "screen" was a triple 1440x900) running on a dual head display card) --- being restricted to two SINGLE monitors running in twinview has severely affected my productivity. While I am a software and systems developer, I do not program in "C", so I am not comfortable or knowlegable in how to "patch" files and recompile them under Linux --- and cannot afford to lose my system again for weeks on end like what happened with the upgrade to 12.04.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/885989 Title: white screen on second monitor when using two xsessions Status in Nautilus: Confirmed Status in “nautilus” package in Ubuntu: Confirmed Status in “nautilus” source package in Precise: Confirmed Bug description: If enable dual head mode (two X screens), the second monitor went white after login with unity or unity-2d. After tracking the gnome- session, it is caused by running "nautilus -n" for this configuration. And if kill the nautilus process, the desktop showed up normally on second screen. lsb_release -rd Description:Ubuntu 11.10 Release:11.10 apt-cache policy nautilus nautilus: Installed: 1:3.2.1-0ubuntu2 Candidate: 1:3.2.1-0ubuntu2 Version table: *** 1:3.2.1-0ubuntu2 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.2.0-0ubuntu5 0 500 http://cn.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/885989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pat
Dave, Restoring the original libcario module fixed evince --- now NX is unable to display text again. Not being real familiar with the internals of Linux, It never occurred to me to relate the loss of EVINCE with the fix of NX --- especially since they occurried weeks apart from each other. - - - - http://ubuntuforums.org/showthread.php?t=2081746&highlight=nomachine I just went out and reread the "fix" description on NX and found that there are new updates to that report. Originally there were only comments 1 to 5. Now there are comments 6 to 12. apparently other people had the same trouble as I did --- and as I was badly burned by the last attempt to fix NX, I do not want to get burned again. Would you be so kind, as to review those comments and see if there is a "recommended" fix for NX? As I still consider myself a relatively "newbee" in Linux, I would appreciate the assistance.) If that is against the rules, then I understand and greatly appreciate the assistance that you have provided!!! /s/ Bill Turner, wb4alm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1093946 Title: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pattern_begin_patch] Status in “evince” package in Ubuntu: Incomplete Bug description: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1093946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pat
Dave, additional info My initial ubuntu distro was Ubuntu 8:04 LTS, which was upgraded to Ubuntu 10.04 LTS, which was upgraded to ubuntu 12.04, and then to 12.10 - - - - To get Gnome 3, I installed "Ubuntu Gnome remix" as outlined here: https://wiki.ubuntu.com/UbuntuGNOME/ReleaseNotes/12.10 This did install a ppa: ppa:gnome3-team/gnome3 and Synaptic Package Manager shows the following PPA: LP-PPA-gnome3-team-gnome3/quantal - - - - /s/ Bill -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1093946 Title: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pattern_begin_patch] Status in “evince” package in Ubuntu: Incomplete Bug description: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1093946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pat
By the way, Dave, I am very appreciative of your assistance. I guess I owe you a cup of coffie, or a stein of something stronger -- which ever you prefer!!! /s/ Bill Turner, wb4alm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1093946 Title: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pattern_begin_patch] Status in “evince” package in Ubuntu: Incomplete Bug description: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1093946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pat
bill@WB4ALM-07:~$ sudo apt-get dist-upgrade [sudo] password for bill: xxx Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. - - - - - sudo apt-get remove libpoppler-glib2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gcc-4.7-arm-linux-gnueabihf-base gir1.2-clutter-gst-2.0 gir1.2-gtkclutter-1.0 gir1.2-rest-0.7 gir1.2-tracker-0.14 gir1.2-zpj-0.0 gwibber libgwibber-gtk3 libzapojit-0.0-0 unoconv Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: libpoppler-glib2 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 225 kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 1089809 files and directories currently installed.) Removing libpoppler-glib2 ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libcairo.so.2 is not a symbolic link bill@WB4ALM-07:~$ - - - - sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: gcc-4.7-arm-linux-gnueabihf-base gir1.2-clutter-gst-2.0 gir1.2-gtkclutter-1.0 gir1.2-rest-0.7 gir1.2-tracker-0.14 gir1.2-zpj-0.0 gwibber libgwibber-gtk3 libzapojit-0.0-0 unoconv 0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded. After this operation, 1,694 kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 1089800 files and directories currently installed.) Removing gcc-4.7-arm-linux-gnueabihf-base ... Removing gir1.2-clutter-gst-2.0 ... Removing gir1.2-gtkclutter-1.0 ... Removing gir1.2-zpj-0.0 ... Removing gir1.2-rest-0.7 ... Removing gir1.2-tracker-0.14 ... Removing gwibber ... Removing libgwibber-gtk3 ... Removing libzapojit-0.0-0 ... Removing unoconv ... Processing triggers for hicolor-icon-theme ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for gnome-menus ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libcairo.so.2 is not a symbolic link Processing triggers for doc-base ... Processing 1 removed doc-base file... Registering documents with scrollkeeper... Processing triggers for man-db ... bill@WB4ALM-07:~$ - - - - - - - That message about "libcairo.so.2" bothers me so... bill@WB4ALM-07:~$ locate libcairo.so.2 /home/bill/.mozilla/firefox/lna9hl72.default/extensions/vmwarev...@vmware.com/plugins/lib/libcairo.so.2 /home/bill/.mozilla/firefox/lna9hl72.default/extensions/vmwarev...@vmware.com/plugins/lib/libcairo.so.2/libcairo.so.2 /home/bill/Download/NoMachine/libcairo/usr/lib/x86_64-linux-gnu/libcairo.so.2 /home/bill/Download/NoMachine/libcairo/usr/lib/x86_64-linux-gnu/libcairo.so.2.11000.2 /home/bill/src/VMware/Linux/VMserver_2.0.2/extracted_vmrc/plugins/lib/libcairo.so.2 /home/bill/src/VMware/Linux/VMserver_2.0.2/extracted_vmrc/plugins/lib/libcairo.so.2/libcairo.so.2 /home/bill/vmware/vmrc-workaround/plugins/lib/libcairo.so.2 /home/bill/vmware/vmrc-workaround/plugins/lib/libcairo.so.2/libcairo.so.2 /usr/lib/i386-linux-gnu/libcairo.so.2 /usr/lib/i386-linux-gnu/libcairo.so.2.11200.2 /usr/lib/vmware/lib/libcairo.so.2 /usr/lib/vmware/lib/libcairo.so.2/libcairo.so.2 /usr/lib/vmware-installer/2.1.0/lib/lib/libcairo.so.2 /usr/lib/vmware-installer/2.1.0/lib/lib/libcairo.so.2/libcairo.so.2 /usr/lib/x86_64-linux-gnu/libcairo.so.2 /usr/lib/x86_64-linux-gnu/libcairo.so.2.11000.2 /usr/lib/x86_64-linux-gnu/libcairo_orig/libcairo.so.2 /usr/lib/x86_64-linux-gnu/libcairo_orig/libcairo.so.2.11200.2 bill@WB4ALM-07:~$ - - - - ls -all /usr/lib/x86_64-linux-gnu/libcairo.so.2 -rw-r--r-- 1 root root 766024 Dec 9 09:48 /usr/lib/x86_64-linux-gnu/libcairo.so.2 According to my manual log for December 9th, the only thing I did was to fix "NX" which my wife uses to access her account on my Linux box via her Win7 desktop.. My notes say: **QUOTE** http://ubuntuforums.org/showthread.php?t=2081746&highlight=nomachine Here are the steps I followed for my 64-bit install of Ubuntu 12.10. I suppose the workaround is the same for the 32-bit version, except you change the libcairo package and the file system paths accordingly: 1. Terminate your NX sessions 2. cd ~/Downloads 3. wget http://mirror.pnl.gov/ubuntu//pool/main/c/cairo/libcairo2_1.10.2-6.1ubuntu2_amd64.deb 4. mkdir libcairo 5. dpkg -x libcairo2_1.10.2-6.1ubuntu2_amd64.deb libcairo/ 6. sudo mkdir /usr/lib/x86_64-linux-gnu/libcairo_orig 7. sudo mv /usr/lib/x86_64-linux-gnu/libcairo.so.2* /usr/lib/x86_64-linux-gnu/libcairo_orig/ 8. su
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade [-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pat
bill@WB4ALM-07:~$ dpkg -l \*libpoppler\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==-=== ii libpoppler-glib20.6.4-1ubuntu3.4 amd64 PDF rendering library (GLib-based shared library) rc libpoppler-glib40.12.4-0ubuntu5.2 amd64 PDF rendering library (GLib-based shared library) ii libpoppler-glib8:amd64 0.20.4-0ubuntu1amd64 PDF rendering library (GLib-based shared library) rc libpoppler-qt4-3:amd64 0.18.4-1ubuntu2amd64 PDF rendering library (Qt 4 based shared library) rc libpoppler19:amd64 0.18.4-1ubuntu2amd64 PDF rendering library ii libpoppler2 0.6.4-1ubuntu3.4 amd64 PDF rendering library ii libpoppler28:amd64 0.20.4-0ubuntu1amd64 PDF rendering library rc libpoppler5 0.12.4-0ubuntu5.2 amd64 PDF rendering library bill@WB4ALM-07:~$ dpkg -l \*libcairo\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==-==-=== un libcairo-dev(no description available) ii libcairo-gobject2:amd64 1.12.2-1ubuntu2.2 amd64 The Cairo 2D vector graphics library (GObject library) ii libcairo-gobject2:i386 1.12.2-1ubuntu2.2 i386 The Cairo 2D vector graphics library (GObject library) ii libcairo-perl 1.100-0ubuntu1 amd64 Perl interface to the Cairo graphics library un libcairo-ruby (no description available) un libcairo-ruby1.8(no description available) ii libcairo-script-interpreter 1.12.2-1ubuntu2.2 amd64 The Cairo 2D vector graphics library (script interpreter) ii libcairo2:amd64 1.12.2-1ubuntu2.2 amd64 The Cairo 2D vector graphics library ii libcairo2:i386 1.12.2-1ubuntu2.2 i386 The Cairo 2D vector graphics library ii libcairo2-dev 1.12.2-1ubuntu2.2 amd64 Development files for the Cairo 2D graphics library un libcairo2-doc (no description available) un libcairomm-1.0-0(no description available) ii libcairomm-1.0-1:amd64 1.10.0-1ubuntu2amd64 C++ wrappers for Cairo (shared libraries) bill@WB4ALM-07:~$ I was on Ubuntu 10.04 LTS and "accidentally" hit the upgrade button for 12.04.1 (wasn't prepared to do an upgrade at that time). I went ahead and let to do the install and immediately ran into a number of problems, including the fact that the system would not reboot when the installation was done. All reboot attempts resulted in a black screen. I was able to trace the problem to a missing command in GRUB (I had GRUB 1 with Ubuntu 10.04) After fixing that problem about a week later GRUB was automatically updated to GRUB2. Personally I do not like the UNITY interface, it requires far too many clicks and menu for be to get anything done. I added KDE per recommendations on several of the Ubuntu forums, and that worked for about a week until a MAJOR ubuntu update came thru and messed up KDE. So I "uninstalled" KDE and tried to use UNITY, but again found it not to my liking. About that time I received an "announcement" that "gnome 3" was available (I do not remeber what the package was called.) I installed that, and started getting a working system again (Took almost 3-4 weeks!!!) After running with the GNOME3 (it always goes into FALLBACK mode, because it thinks my graphics card (EVA nvidia GeForce 9600GTS) is not 3d capable - which it is...) A suggestion was to upgrade once again to 12.10, which I did. Things have been kinda stable since, and have found workarounds for all of the little bugs (like having to run SYSLOG in a terminal screen to get it to work at all, and having to put up with the missing timestamps on each line 'cause they are displayed in white ink, on a white background) I currently log on with GNOME and most things work - except for evince. This is a major problem to me, as almost all of the documentation that I use are in PDF files... After some investigation I found "mupdf" which
[Desktop-packages] [Bug 1093946] Re: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade
Good thought, never thought about trying to run evince in a terminal session... The answer is that it still fails and I get the following message: (evince:16765): EvinceDocument-WARNING **: /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8: undefined symbol: cairo_mesh_pattern_begin_patch Segmentation fault (core dumped) I get the same message, no matter what PDF file I try to open. (Tried several) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1093946 Title: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade Status in “evince” package in Ubuntu: Incomplete Bug description: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1093946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1093946] [NEW] Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade
Public bug reported: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1093946 Title: Evince fails to open PDF files. worked prior to Ubuntu 12.10 upgrade Status in “evince” package in Ubuntu: New Bug description: Any time I try to view a PDF file, an icon is created in the task bar that says "opening file " but the file does not open. No errors are shown and I have not located any messages in any of the logs. This problem affects ALL pdf files, but the files are displayable using "mupdf". According to the following, evince 3.6.0 is installed. apt-cache policy evince evince: Installed: 3.6.0-0ubuntu2 Candidate: 3.6.0-0ubuntu2 Version table: *** 3.6.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status I have attempted to purge and reinstall evince several times, even to the point of deleting the evince libraries in /usr/lib/ and /usr/share/ and /var/lib/dpkg/info/ The result is always the same. Sometimes after the failure, Ubuntu reports an internal error in evince - which I have told it to send a report to the developers. The report must be very small, as it takes less than a second to do so. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evince 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Wed Dec 26 22:25:34 2012 MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to quantal on 2012-11-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1093946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034156] Re: System Log will not launch
I have "applied" all outstanding updates for my Ubuntu 12.10 system as of 12:57 (noon) 5 Dec 2012... When system log is launched, no password prompt is made, no messages are displayed, etc. Therefore the bug has still not been fixed. (I can how ever run the program from a terminal session. - it jkust will not run when launched from the main menu.) /s/ Bill Turner, wb4alm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1034156 Title: System Log will not launch Status in “policykit-1” package in Ubuntu: Confirmed Bug description: After updating to quantal my menu entry named System Log will not launch After checking the menu entry properties I saw that the associated command was 'pkexec gnome-system-log'. If I run this command at a terminal window, it will ask for my password and then it shows the gnome-system-log window as is supposed to. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-8-generic 3.5.0-8.8 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorgehsrama 2173 F pulseaudio Date: Tue Aug 7 22:14:04 2012 HibernationDevice: RESUME=UUID=8170e72c-3b1e-48b8-9dd3-f93f30791e6a InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) Lsusb: Bus 001 Device 004: ID 0011:7788 Bus 001 Device 002: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic root=UUID=0a689cc1-8f39-4ff3-8297-878646ffed1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-8-generic N/A linux-backports-modules-3.5.0-8-generic N/A linux-firmware 1.88 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-07-28 (10 days ago) dmi.bios.date: 09/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr218:bd09/21/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1034156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034156] Re: System Log will not launch
I do not understand assignment to "wishlist"... I have always been able to launch from menu, now I can't... ...therefore this is not a "wishlist", but is a bug introduced with 12.04.1 and continued in 12.10 furthermore, the message in .xsession-errors: "Refusing to render service to dead parents." indicates that something is just plain wrong! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1034156 Title: System Log will not launch Status in “policykit-1” package in Ubuntu: Confirmed Bug description: After updating to quantal my menu entry named System Log will not launch After checking the menu entry properties I saw that the associated command was 'pkexec gnome-system-log'. If I run this command at a terminal window, it will ask for my password and then it shows the gnome-system-log window as is supposed to. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-8-generic 3.5.0-8.8 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorgehsrama 2173 F pulseaudio Date: Tue Aug 7 22:14:04 2012 HibernationDevice: RESUME=UUID=8170e72c-3b1e-48b8-9dd3-f93f30791e6a InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) Lsusb: Bus 001 Device 004: ID 0011:7788 Bus 001 Device 002: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic root=UUID=0a689cc1-8f39-4ff3-8297-878646ffed1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-8-generic N/A linux-backports-modules-3.5.0-8-generic N/A linux-firmware 1.88 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2012-07-28 (10 days ago) dmi.bios.date: 09/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr218:bd09/21/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1034156/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp