[Bug 1216594] [NEW] xfce power manager reports invalid battery life information
Public bug reported: the xfce4-power-manager is having some issues in determining how much battery life is left on my laptop. primarily, if i unplug my laptop from the adapter the following message appears: "System is running on battery power. your battery is discharging. Estimated time left is 13 Hours 59 minutes." however, i know that my battery only last for about 2:10. after idling the computer for about 5 minutes, it now states: "System is running on battery power. your battery is discharging. Estimated time left is 1 Hours 29 minutes." and will then fluctuate between ~15 minutes+ more and ~15 minutes less, until the systems is at 10% charge, then it drops to 30 mins. Running Ubuntu 13.04 xfce4-power-manager: Installed: 1.2.0-1ubuntu2 Candidate: 1.2.0-1ubuntu2 Version table: *** 1.2.0-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xfce4-power-manager 1.2.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Aug 25 11:12:30 2013 ExecutablePath: /usr/bin/xfce4-power-manager InstallationDate: Installed on 2012-12-13 (255 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to raring on 2013-08-07 (18 days ago) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216594 Title: xfce power manager reports invalid battery life information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1216594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529430] [NEW] smbclient comepltely Incompatible with Nintendo 3DS MicroSD Devices
Public bug reported: the Linux smbclient is physically incompatible with Nintendo 3ds Devices the SMB protocol the devices use do not match any existing linux protocols. Several attempts were made to connect to a device "3ds1": Attempt #1: Inside Firefox on Ubuntu 15.10: "smb://3ds1/microSD" does absolutely nothing. Attempt #2: from Nautilus using the terminal command "sudo nautilus smb://3ds1/microSD" throws an error. "Unable to display all the files "Operation not supported"". Terminal displays several "Bus connection Refused" errors. Nautilus soft hangs, requiring a manual kill from terminal. Attempt #3: from a non-root Nautilus using the terminal command "nautilus smb://3ds1/microSD". unlike before, you get a login prompt, which is required since the 3ds device requires a password to login to the microSD. entering the correct password crashes nautilus. Entering an incorrect password throws an error "Unsupported NT status". Attempt #4: manually using smbclient from terminal using the terminal command "smbclient 3ds1/microSD". after entering the password for the device, smbclient throws the error "Unsupported NT Status". running "smbclient -L 3ds1/microSD" throws instead "NT_STATUS_INVALID_NETWORK_RESPONSE". Final Attempt #5: forcing a CIFS mount using the mount terminal command "mount -t cifs 3ds1/MicroSD /media/3ds -o username=axil,password=abc123,nounix" fails instantly. the following is given from the command "dmesg | tail": [76742.710850] Key type cifs.spnego registered [76742.710855] Key type cifs.idmap registered [76742.711000] CIFS VFS: Malformed UNC in devname. [76762.270863] CIFS VFS: Malformed UNC in devname. [76910.770391] Unable to determine destination address. [78759.909740] nautilus[1668]: segfault at 15d ip 7fa5fafb9ce4 sp 7ffefb6c2fb0 error 4 in libgtk-3.so.0.1600.7[7fa5fad2+6de000] [79694.842478] CIFS: bad ip= option (3dsIP). [79710.028841] CIFS: bad ip= option (3dsIP). [79717.386602] CIFS VFS: Malformed UNC in devname. [79770.039655] CIFS VFS: Malformed UNC in devname. certain users have been able to get mount to attempt to load it but it stalls during the mount procedure, or it breaks when an "ls" command is entered into terminal. It would appear that nautilus can't handle whatever smbclient protocol is being fed by the 3ds. this device works under windows perfectly. the device is not at fault. all linux users with 3ds devices are reporting similar issues. Release version: Description:Ubuntu 15.10 Release:15.10 smbclient: Installed: 2:4.1.17+dfsg-4ubuntu3 Candidate: 2:4.1.17+dfsg-4ubuntu3 Version table: *** 2:4.1.17+dfsg-4ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:4.1.17+dfsg-4ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages i expected nautilus to see the device in the "browse network" subirectory, but it fails to appear, along with smbclient not being able to recognize the device at all. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: 3ds error nautilus smbclient ubuntu ** Package changed: ubuntu => samba (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529430 Title: smbclient comepltely Incompatible with Nintendo 3DS MicroSD Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1529430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525056] Re: nouveau: Probe of 0000:03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2"
Tested on the latest CDImage: The installer works fine, but a similar error occured (copied from dmesg) nouveau :03:00.0: unknown chipset (118010a2) [3.796605] nouveau: probe of :03:00.0 failed with error -12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525056 Title: nouveau: Probe of :03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1525056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525056] Re: nouveau: Probe of 0000:03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2"
you can close this bug 16.04 corrected the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525056 Title: nouveau: Probe of :03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1525056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525056] [NEW] nouveau: Probe of 0000:03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2"
Public bug reported: Fresh, clean install of Ubuntu 15.10 threw this on first boot. When installing, i had to select "Try Ubuntu" (Boot to the desktop). Selecting "Install Ubuntu" threw a fatal Ubiquity error loop. in that case the main cause was determined to be Ubiquity not being able to detect my Graphics Chip, a Combination Intel HD graphics chip and an Nvida 840m chip. the errors in question: nouveau ![ DEVICE][:03:00.0] unknown Maxwell chipset [0.734866] nouveau E[ DEVICE][:03:00.0] unknown chipset, 0x118010a2 [0.734868] nouveau E[ DRM] failed to create 0x0080, -22 [0.735125] nouveau: probe of :03:00.0 failed with error -22 distribution: Description:Ubuntu 15.10 Release:15.10 Nouveau Version: Installed: 1:1.0.11-1ubuntu3 Candidate: 1:1.0.11-1ubuntu3 Version table: *** 1:1.0.11-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status A better description of the ubiquity Problem: the screen appeared in greyscale. the installer immediately threw a Ubiquity fatal error, then dropping to a oddly spaced message screen with an error, "Failed to load login", or to that effect. Eventually, after 5-6 minutes, a message stating that X.org "Failed to determine my graphics card", asking me to select default setting, which also failed. reloading it in desktop mode, then installing fixed this issue, and i was able to install successfully ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 10 21:56:18 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14ad] Subsystem: ASUSTeK Computer Inc. Device [1043:14ad] InstallationDate: Installed on 2015-12-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. N56JN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=ae643564-5872-4f16-8efe-5db0f9356be6 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56JN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56JN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56JN.203:bd05/12/2014:svnASUSTeKCOMPUTERINC.:pnN56JN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56JN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56JN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Dec 11 02:16:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14061 vendor AUO xserver.version: 2:1.17.2-1ubuntu9 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525056 Title: nouveau: Probe of :03:00. 0 failed with error -22 "Unknown maxwell chipset", "Unknown Chipset, 0x118010A2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bu
[Bug 1203899] [NEW] NPAPI Flash plugin freezes chrome, firefox
Public bug reported: If i disable PPAPI Flash Plugin in chrome, then try to run a flash object (YouTube video, flash game, etc...) chrome will hang causing me to force restart. this seems to only happen with the NPAPI plugin (11.2 r202 of libflashplayer.so) firefox SEEMS to start working AFTER I installed chrome, as it provided it's own version of flash. (PPAPI plugin) (I cannot create the firefox crashes after i installed chrome. maybe it delegates flash to other programs?) OS: Description:Ubuntu Saucy Salamander (development branch) Release:13.10 FireFox: firefox23.0~b4+buil amd64 Chrome: 28.0.1500.71 (Official Build 209842) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: saucy verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203899 Title: NPAPI Flash plugin freezes chrome, firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1203899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
