[Bug 204670] [NEW] Epson Stylus DX4450 All in Oneprinter/scanner won't work, I've tried to load Epson Avasys drivers but they won't load
Public bug reported: Binary package hint: gnome-panel Epson Stylus DX4450 All in Oneprinter/scanner won't work, I've tried to load Epson Avasys drivers but they won't load ProblemType: Bug Architecture: i386 Date: Fri Mar 21 14:33:15 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 1:2.20.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/jim ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel Uname: Linux Chocolate 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Epson Stylus DX4450 All in Oneprinter/scanner won't work, I've tried to load Epson Avasys drivers but they won't load https://bugs.launchpad.net/bugs/204670 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204670] Re: Epson Stylus DX4450 All in Oneprinter/scanner won't work, I've tried to load Epson Avasys drivers but they won't load
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/12789101/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/12789102/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/12789103/ProcStatus.txt -- Epson Stylus DX4450 All in Oneprinter/scanner won't work, I've tried to load Epson Avasys drivers but they won't load https://bugs.launchpad.net/bugs/204670 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663241] [NEW] Palm Zire 21 won't sync with Evolution in Maverick 10.10
Public bug reported: Binary package hint: evolution Synchronization worked fine before I upgraded to Ubuntu 10.10 - the Maverick Meerkat from the previous version The conduits are not recognized so the machines wont sync ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu6 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic-pae 2.6.35.4 Uname: Linux 2.6.35-22-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Oct 19 13:19:46 2010 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash LANG=en_GB.utf8 SourcePackage: evolution XsessionErrors: (polkit-gnome-authentication-agent-1:1768): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1741): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- Palm Zire 21 won't sync with Evolution in Maverick 10.10 https://bugs.launchpad.net/bugs/663241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663241] Re: Palm Zire 21 won't sync with Evolution in Maverick 10.10
-- Palm Zire 21 won't sync with Evolution in Maverick 10.10 https://bugs.launchpad.net/bugs/663241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663241] Evolution Synchronization
To Sebastien Bacher Thank you for looking at my problem, Please can you give me any idea on how I would go about looking upstream to solve my problem. Regards Jim Aird -- Palm Zire 21 won't sync with Evolution in Maverick 10.10 https://bugs.launchpad.net/bugs/663241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663241] Evolution Synchronization
To Sebastien Bacher Thank you for looking at my problem, Please can you give me any idea on how I would go about looking upstream to solve my problem. Regards Jim Aird -- Palm Zire 21 won't sync with Evolution in Maverick 10.10 https://bugs.launchpad.net/bugs/663241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789107] [NEW] upgrade from 17.10 to 18.04 crashed at about 80% complete. I have never been able to run this computer properly since I wiped windows 10 to install Ubuntu
Public bug reported: I suspect Microsoft is blocking me out. It is crashing less since I started getting firmware upgrades, The Kernel may be the problem I'm not very knowledgeable on computers. My computer is a HP ENVY ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 26 15:08:48 2018 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a5b90a9d-3c30-4782-96b4-4961763fa6c2 ro quiet splash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-26 (0 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789107 Title: upgrade from 17.10 to 18.04 crashed at about 80% complete. I have never been able to run this computer properly since I wiped windows 10 to install Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1789107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1789107] Re: upgrade from 17.10 to 18.04 crashed at about 80% complete. I have never been able to run this computer properly since I wiped windows 10 to install Ubuntu
*** This bug is a duplicate of bug 1788727 *** https://bugs.launchpad.net/bugs/1788727 Bug 1789107 I sent a document to HP and UEFI asking for help, both were ignored. A second letter was sent to HP, that was also ignored. A boot USB was able to install Ubuntu but the computer would not run ubuntu at that time. When the main processor manufacturers found out that there were faults in their CPU’s Ubuntu made changes to there firmware. When I noticed the word “firmware” when I was installing the updates for me other machine, I got the HP machine out of the cupboard, after many attempts it worked once. After the next few weeks. I managed run Ubuntu about 5 times, not good but it gave me hope. I installed Ubuntu 17 10 it worked better but still not perfect. I tried to install Ubuntu 18 04 from a USB stick , it would not install so I tried to upgrade from Ubuntu 17 10, the upgrade kept crashing. That is when someone wondered what on earth is going on down there? On Wed, 29 Aug 2018 at 18:06, Phillip Susi wrote: > > *** This bug is a duplicate of bug 1788727 *** > https://bugs.launchpad.net/bugs/1788727 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1788727, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Please continue to report any other bugs you may > find. > > ** This bug has been marked a duplicate of bug 1788727 >upgrade crashing due to unsigned kernels > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1789107 > > Title: > upgrade from 17.10 to 18.04 crashed at about 80% complete. I have > never been able to run this computer properly since I wiped windows 10 > to install Ubuntu > > Status in grub2 package in Ubuntu: > New > > Bug description: > I suspect Microsoft is blocking me out. It is crashing less since I started > getting firmware upgrades, > The Kernel may be the problem > I'm not very knowledgeable on computers. > My computer is a HP ENVY > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: grub-efi-amd64 2.02-2ubuntu8.3 > ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 > Uname: Linux 4.13.0-21-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > Date: Sun Aug 26 15:08:48 2018 > ErrorMessage: installed grub-efi-amd64 package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2018-08-26 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20180105.1) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic > root=UUID=a5b90a9d-3c30-4782-96b4-4961763fa6c2 ro quiet splash > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3ubuntu1 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.3ubuntu0.1 > SourcePackage: grub2 > Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: > installed grub-efi-amd64 package post-installation script subprocess returned > error exit status 1 > UpgradeStatus: Upgraded to bionic on 2018-08-26 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1789107/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789107 Title: upgrade from 17.10 to 18.04 crashed at about 80% complete. I have never been able to run this computer properly since I wiped windows 10 to install Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1789107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1788727] Re: upgrade crashing due to unsigned kernels
To Sandi Vujakovic Is it possible to send me an instruction that I can type into my computer. I can copy and paste into terminal. regards Jim Aird On Fri, 7 Sep 2018 at 21:03, Sandi Vujaković <1788...@bugs.launchpad.net> wrote: > > The workaround that I have is removing all UKUU added/mainline kernels, > finish configuring the grub packages, reinstall the latest mainline > kernel and be on my marry way. > > If it installed unsigned versions alongside the signed ones, then the > UKUU kernels removed should have no effect on that. Also, if you can't > boot with unsigned kernels no matter what when Secure Boot is on, then > how come I don't have to turn it off after reinstalling the mainline > kernels and the system boots just fine (and yes, I checked)? > > It gives me the impression that Secure Boot only looks at GRUB and > doesn't really see the kernels. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1789107). > https://bugs.launchpad.net/bugs/1788727 > > Title: > upgrade crashing due to unsigned kernels > > Status in grub2 package in Ubuntu: > Confirmed > > Bug description: > not surre happened during upgrade to bionic beaver > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: grub-efi-amd64 2.02-2ubuntu8.3 > Uname: Linux 4.7.0-040700-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > Date: Thu Aug 23 19:33:07 2018 > ErrorMessage: installed grub-efi-amd64 package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2018-05-30 (85 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-040700-generic > root=UUID=d9d727a6-5798-4fe1-8ac0-fb79b1d05431 ro quiet splash vt.handoff=7 > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3ubuntu1 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.3ubuntu0.1 > SourcePackage: grub2 > Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: > installed grub-efi-amd64 package post-installation script subprocess returned > error exit status 1 > UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788727 Title: upgrade crashing due to unsigned kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1788727] Re: upgrade crashing due to unsigned kernels
Sandi, I hope this is the correct procedure reporting via you. Thanks for the email. My HP system seems a little different than yours, I finished up with the two latest kernels and a warning that I also had an old kernel that was not of the secure boot (efi) variety. I deleted the old kernel, to find later that it was the old kernel that worked best occasional. I cannot directly install Ubuntu 20.18 from a USB stick, it wont even load up. I managed to install Ubuntu 17.10 then upgrade to Ubuntu 20.18 The first non efi kernel was 4.13.0-21-generic. I upgraded from Ubuntu 17.10, and am informed that a non efi kernel 4.13.0-46-generic has appeared and prevents completion, I have deleted this kernel. After aprox 20 boots I gave up trying to get into the computer. (there is no logic in getting the computer to boot up, the more I try the less chance of success). Next day Five attempts booting with kernel 4.15.0-3-generic failed, third attempt with kernel 4.13.0-21-generic success A crash happened on the HP pc this morning and I was asked if I could supply any data, hence this email. I hope this information reaches all concerned and is of use. Regards Jim On Wed, 12 Sep 2018 at 00:00, Sandi Vujaković <1788...@bugs.launchpad.net> wrote: > > Jim, I only know the GUI way of doing it. I select all of the kernels > above 4.15.xx and select remove, but only once I have booted up with the > older kernel (once the GRUB menu appears, go into Advanced options and > look for 4.15 and boot off of that, just don't select "(recovery > mode)"), type "apt autoremove", but since you probably don't use the > terminal logged in as root in it, type in "sudo apt autoremove" and it > should automatically start configuring the packages that were not > configured previously, a.k.a. the GRUB updates, open UKUU, install the > latest available kernel, restart and enjoy! > > Do note that I am using an HP laptop and that a previous GRUB update (a > few months ago) enrolled new Secure Boot keys, which might affect the > fact that I'm booting with unsigned kernels and Secure Boot on. > > Good luck and have a nice day! > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1789107). > https://bugs.launchpad.net/bugs/1788727 > > Title: > upgrade crashing due to unsigned kernels > > Status in grub2 package in Ubuntu: > Confirmed > > Bug description: > not surre happened during upgrade to bionic beaver > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: grub-efi-amd64 2.02-2ubuntu8.3 > Uname: Linux 4.7.0-040700-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > Date: Thu Aug 23 19:33:07 2018 > ErrorMessage: installed grub-efi-amd64 package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2018-05-30 (85 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-040700-generic > root=UUID=d9d727a6-5798-4fe1-8ac0-fb79b1d05431 ro quiet splash vt.handoff=7 > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3ubuntu1 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.3ubuntu0.1 > SourcePackage: grub2 > Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: > installed grub-efi-amd64 package post-installation script subprocess returned > error exit status 1 > UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788727 Title: upgrade crashing due to unsigned kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1788727] Re: upgrade crashing due to unsigned kernels
Sandi, Answer to your last question first, I am a pensioner, I write slow, make mistakes, (hence 20.18 should read 18.04), I need a good spell checker, so I use writer to prepare what I want to say then I paste it into the email, I must remember to paste as raw text in future. The computer that I am having problems with is as follows :- HP ENVY 15-AH151s 15.6" Laptop - AMD A10-8700P - 8GB Ram - 1TB HDD - Bang & Olufsen Audio Win10 Sold second hand by Amazon/Luzern, It arrived Saturday, June 25 2016 The computer came with windows 10 installed. My plan was to remove windows 10 and install Ubuntu 16.04. I had previously converted three desktop and two laptop PCs to Ubuntu without any problems, the latter being a Lenovo G50-70 Laptop converted from window 8 and is now running Ubuntu 18.04 I set the HP Notebook to Legacy Bios and disabled fast boot. Startup Disk Creator was used to make a boot USB, with witch I used the “try Ubuntu” option to ensure Ubuntu would run on this machine, all seemed OK so I started the install procedure. I chose to use the whole hard disk for Ubuntu as I don’t use Microsoft. The install went fine, all complete I was instructed to re boot, a black screen was the result. I rebooted into setup mode and selected the ubuntu option and got a screen full of cascading code. I booted with the USB in the “try Ubuntu” mode, all the Ubuntu file had been installed but the uefi would not let them load I took the computer to a computer repair shop, the man said it will be ready in 24 hours. Five weeks later he gave me the PC back and said it was something microsoft or HP had done wrong! Over the months that followed I saw many different screens, Ubuntu logo, static code, blank screen etc! I list things I have tried in many combinations (Note, I can copy and paste code but compiling code is beyond me). Gparted, Boot repair, Disks, re formatted the hard drive in both MBR and GPT, Legacy Bios and Secure Boot. When I click on “disks” I see the following three devices, 1.0 TB Hard Disk WDC WD10JPVX-60JC3TO 1.0 GB Drive Generic Flash Disk, (this is my USB boot drive) 1.5 GB Loop Device /cdrom/casper/filesystem.squashfs I think the Loop Device is the cause of the problem. I’ve tried to delete the Loop Device and or the rofs directory but they won’t let me. I was hoping this would allow me to run Ubuntu in legacy BIOS mode. After about a year of trying all sorts to get the computer to work I sort of gave up. When the CPU manufactures where found out to have been making faulty processors the computer manufactures started modifying firmware and software to get round the problem. I got my sick laptop out of the cupboard to see if it would work, after many weeks of trying different ways of installing and trying to boot Ubuntu it suddenly booted up, but it was several more weeks before I got it to boot up again. I never seems to boot up the same way twice, When I managed to get the machine going occasionally with 17.10 in efi but never in legacy bios mode. When I first tried to install 18.04 by usb it would not load but it did the last time ai tried. The ratio booting up can be anything between first time and giving up after 50 attempts UKUU (Ubuntu Kernel Update Utility) ? I must investigate On Sun, 16 Sep 2018 at 21:25, Sandi Vujaković <1788...@bugs.launchpad.net> wrote: > > Forewarning, I began switching to Antergos one day after your post and > finished today, so I will not be able to provide any more hands-on data, > since Antergos is an Arch-based distribution (tried to install Arch in a > VM twice, failed both times). I switched because I was trying to make my > Ubuntu install into a rolling one, so why not switch to a proper rolling > one, like say Arch (or an Arch-based one, like Antergos). I had to > disable Secure Boot though, so it defeats the purpose of this bug (yes, > it seems that Arch kernels are unsigned), but whatever. > > It seems that you misunderstood me, at least a bit. The older kernels are the > ones you're not supposed to remove during this procedure. I am not sure about > the upgrade being interrupted by the newer kernels, but I didn't try UKUU > before 18.04 anyway (speaking of which, did you mean 18.04 when you wrote > 20.18?). > Also, the kernels aren't "efi" and "non-efi", they're signed and unsigned, > reflecting whether or not they would pass under Secure Boot, though it seems > that my laptop doesn't care after GRUB is loaded, which is signed by > Canonical as well (speaking of which, what's the model of your laptop? the > number should be on the underside of it if it's a newer model, probably 2014 > and later, but definitely 2016 and later, mine's 15-aw003nm). > > Could you please clarify what your course of action was after installing > Ubuntu Artful? > > My understanding is that you didn't even touch UKUU (Ubuntu Kernel Update > Utility) on Artful before upgrading to Bionic and not even after the upgrade. > If that is the case,
