[Touch-packages] [Bug 398670] Re: eject: unable to eject, last error: Inappropriate ioctl for device
Also for what it's worth, I was experiencing "eject: unable to eject, last error: Inappropriate ioctl for device", and it turned out that I had an object blocking the tray so it couldn't fully open. When I removed the object, the error went away. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/398670 Title: eject: unable to eject, last error: Inappropriate ioctl for device Status in eject package in Ubuntu: Invalid Bug description: When issuing an "eject" command on the console, I get: $ eject eject: unable to eject, last error: Inappropriate ioctl for device $ dmesg reports: [ 149.469374] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.469380] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.469385] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.469393] end_request: I/O error, dev sr0, sector 0 [ 149.469397] __ratelimit: 68 callbacks suppressed [ 149.469400] Buffer I/O error on device sr0, logical block 0 [ 149.469403] Buffer I/O error on device sr0, logical block 1 [ 149.469407] Buffer I/O error on device sr0, logical block 2 [ 149.469410] Buffer I/O error on device sr0, logical block 3 [ 149.469412] Buffer I/O error on device sr0, logical block 4 [ 149.469415] Buffer I/O error on device sr0, logical block 5 [ 149.469417] Buffer I/O error on device sr0, logical block 6 [ 149.469419] Buffer I/O error on device sr0, logical block 7 [ 149.469422] Buffer I/O error on device sr0, logical block 8 [ 149.469424] Buffer I/O error on device sr0, logical block 9 [ 149.486612] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.486618] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.486623] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.486630] end_request: I/O error, dev sr0, sector 0 [ 149.503096] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.503105] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.503112] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.503121] end_request: I/O error, dev sr0, sector 0 [ 149.505347] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.505360] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.505373] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.505390] end_request: I/O error, dev sr0, sector 0 Even if the CD cannot be read, I should still be able to eject it! $ eject -v eject: using default device `cdrom' eject: device name is `cdrom' eject: expanded name is `/dev/cdrom' eject: `/dev/cdrom' is a link to `/dev/sr0' eject: `/dev/sr0' is not mounted eject: `/dev/sr0' is not a mount point eject: `/dev/sr0' is not a multipartition device eject: trying to eject `/dev/sr0' using CD-ROM eject command eject: CD-ROM eject command failed eject: trying to eject `/dev/sr0' using SCSI commands eject: SCSI eject failed eject: trying to eject `/dev/sr0' using floppy eject command eject: floppy eject command failed eject: trying to eject `/dev/sr0' using tape offline command eject: tape offline command failed eject: unable to eject, last error: Inappropriate ioctl for device $ lsb_release -rd Description: Ubuntu karmic (development branch) Release: 9.10 $ apt-cache policy eject eject: Installed: 2.1.5+deb1+cvs20081104-6 Candidate: 2.1.5+deb1+cvs20081104-6 Version table: *** 2.1.5+deb1+cvs20081104-6 0 500 http://de.archive.ubuntu.com karmic/main Packages 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/398670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 983535] Re: libdvdread: Can't seek to block XXXXX
I've experienced this error with a couple of DVDs on 18.04.1 if I do "vobcopy -m" on some DVDs this error appears. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/983535 Title: libdvdread: Can't seek to block X Status in libdvdread package in Ubuntu: Fix Released Bug description: Same problemlem as described here: https://bugs.launchpad.net/bugs/446664 I'm opening a new bug, because the referred bug expired and it seems to affect Ubuntu 11.10, too. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libdvdread4 4.1.3-10ubuntu4.1 ProcVersionSignature: Ubuntu 3.0.0-19.32-generic 3.0.27 Uname: Linux 3.0.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Apr 17 01:01:33 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, user) LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: libdvdread UpgradeStatus: Upgraded to oneiric on 2011-10-15 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/983535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614942] [NEW] "GLib-CRITICAL" messages keep appearing in log file
Public bug reported: At regular intervals, errors appear in the log files from consolekit: Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: consolekit 0.4.6-5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 13:09:22 2016 InstallationDate: Installed on 2012-03-26 (1606 days ago) InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: consolekit UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago) ** Affects: consolekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1614942 Title: "GLib-CRITICAL" messages keep appearing in log file Status in consolekit package in Ubuntu: New Bug description: At regular intervals, errors appear in the log files from consolekit: Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: consolekit 0.4.6-5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 13:09:22 2016 InstallationDate: Installed on 2012-03-26 (1606 days ago) InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: consolekit UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1614942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
I also get this "bug" about 10 times a day on a mythbuntu box that I barely even use! It could be coming from mythtv-frontend, lightdm, or a programme launched by lightdm. Nov 12 01:39:24 mythtv console-kit-daemon[11843]: GLib-CRITICAL: Source ID 811 was not found when attempting to remove it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471752] [NEW] apport fails to capture Package field when pinger from squid3 crashes
Public bug reported: Summary: The problem is either that apport fails to associate /usr/lib/squid3/pinger with the squid3 package, or that apport-retrace fails to parse a crash report. Apport has captured some information in a crash file (attached) regarding a crash of the pinger process from the squid3 package. When I run apport-retrace, I get the following error message: # apport-retrace -s -S system /var/crash/_usr_lib_squid3_pinger.0.crash ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath The crash report contains the CoreDump, DistroRelease and ExecutablePath fields, but does not contain the Package field. This line appears in the kernel log when pinger crashes: [6017418.123570] pinger[16002]: segfault at 3e822f940098 ip 7f9d3be37845 sp 7ffc798fcbb0 error 4 in libc-2.19.so[7f9d3bdb9000+1bb000] What I expect should happen: apport captures the Package field in the crash report, and apport-retrace is able to process the crash report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-retrace 2.14.1-0ubuntu3.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 640:0:0:58707:2015-07-06 07:54:44.017688187 +0100:2015-07-06 11:28:22.003206431 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash Date: Mon Jul 6 11:38:22 2015 InstallationDate: Installed on 2012-03-26 (1196 days ago) InstallationMedia: Mythbuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-07-20 (350 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: crash file that apport-retrace has trouble with https://bugs.launchpad.net/bugs/1471752/+attachment/4425021/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1471752 Title: apport fails to capture Package field when pinger from squid3 crashes Status in apport package in Ubuntu: New Bug description: Summary: The problem is either that apport fails to associate /usr/lib/squid3/pinger with the squid3 package, or that apport-retrace fails to parse a crash report. Apport has captured some information in a crash file (attached) regarding a crash of the pinger process from the squid3 package. When I run apport-retrace, I get the following error message: # apport-retrace -s -S system /var/crash/_usr_lib_squid3_pinger.0.crash ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath The crash report contains the CoreDump, DistroRelease and ExecutablePath fields, but does not contain the Package field. This line appears in the kernel log when pinger crashes: [6017418.123570] pinger[16002]: segfault at 3e822f940098 ip 7f9d3be37845 sp 7ffc798fcbb0 error 4 in libc-2.19.so[7f9d3bdb9000+1bb000] What I expect should happen: apport captures the Package field in the crash report, and apport-retrace is able to process the crash report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-retrace 2.14.1-0ubuntu3.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 640:0:0:58707:2015-07-06 07:54:44.017688187 +0100:2015-07-06 11:28:22.003206431 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash Date: Mon Jul 6 11:38:22 2015 InstallationDate: Installed on 2012-03-26 (1196 days ago) InstallationMedia: Mythbuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-07-20 (350 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1471752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
