Re: [Bug 1751005] Re: libreoffice cannot open a document not within $HOME
edit /etc/apparmor.d/tunables/alias add the line: alias /home/ -> /data/ On 24.02.2018 10:10, sandeep wrote: > I am also facing the same issue. > > I am using Ubuntu 17.10 as my daily driver. I have created a separate > partition like home for storage /data of ext4 type. > > Today, after updated my system using apt dist-upgrade. I am unable to > access all my documents from /data partition. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1751005 [1] > > Title: > libreoffice cannot open a document not within $HOME > > Status in libreoffice package in Ubuntu: > Fix Committed > > Bug description: > Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1), > files not within the user $HOME directory cannot be opened. This has > nothing to do with ownership or permissions - the target document is > owned by the user with full permissions. Moving the file to ~/Desktop > allows it to be opened normally. > > Error message in popup window: > Access to /home2/mico/documents/personal/2018 lists.ods was denied. > > Error message when launched from terminal: > $: localc "2018 lists.ods" > javaldx: Could not find a Java Runtime Environment! > Please ensure that a JVM and the package libreoffice-java-common is installed. > If it is already installed then try removing > ~/.libreoffice/3/user/config/javasettings_Linux_*.xml > Warning: failed to read path from javaldx > > The file mentioned in the error message does not exist. > I removed the corresponding file under ~/.libreoffice/4/ but that makes no > difference. > > This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with > today's update (Feb. 22) it appeared in Ubuntu 17.10. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1 > ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 > Uname: Linux 4.13.0-36-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Feb 22 09:35:49 2018 > InstallationDate: Installed on 2018-01-27 (25 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) > SourcePackage: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions > [2] Links: -- [1] https://bugs.launchpad.net/bugs/1751005 [2] https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1751005] Re: libreoffice cannot open a document not within $HOME
Exotic? I am a developer and run several different flavors of Linux for testing. I have done this for years for files accessible to all flavors. If the file ownership and permissions are OK, I think I should be able to access them by default. Apparmor seems to be configured to another default - deny access to my owned files if not under $HOME. Is this a good default? On 22.02.2018 13:50, Olivier Tilloy wrote: > No, that's not a solution, because as soon as libreoffice 6 is in the > ubuntu archive it will have the working apparmor profiles. If you want > to disable the apparmor profiles permanently, you can do the following: > > sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.* > /etc/apparmor.d/disable/ > > I'm going to mark this bug invalid as the apparmor profiles are working > as expected, but your setup (with a /home2 mount point) is rather > exotic. > > ** Changed in: libreoffice (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1751005 [1] > > Title: > libreoffice cannot open a document not within $HOME > > Status in libreoffice package in Ubuntu: > Invalid > > Bug description: > Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1), > files not within the user $HOME directory cannot be opened. This has > nothing to do with ownership or permissions - the target document is > owned by the user with full permissions. Moving the file to ~/Desktop > allows it to be opened normally. > > Error message in popup window: > Access to /home2/mico/documents/personal/2018 lists.ods was denied. > > Error message when launched from terminal: > $: localc "2018 lists.ods" > javaldx: Could not find a Java Runtime Environment! > Please ensure that a JVM and the package libreoffice-java-common is installed. > If it is already installed then try removing > ~/.libreoffice/3/user/config/javasettings_Linux_*.xml > Warning: failed to read path from javaldx > > The file mentioned in the error message does not exist. > I removed the corresponding file under ~/.libreoffice/4/ but that makes no > difference. > > This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with > today's update (Feb. 22) it appeared in Ubuntu 17.10. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1 > ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 > Uname: Linux 4.13.0-36-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Feb 22 09:35:49 2018 > InstallationDate: Installed on 2018-01-27 (25 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) > SourcePackage: libreoffice > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions > [2] Links: -- [1] https://bugs.launchpad.net/bugs/1751005 [2] https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1751005] Re: libreoffice cannot open a document not within $HOME
After getting over the confusion caused by your example, and inputting
the entire command on one line, it did solve the problem. Thanks. The
diagnostic could have been less cryptic.
On 22.02.2018 12:06, Olivier Tilloy wrote:
> The error message about
> ~/.libreoffice/{3,4}/user/config/javasettings_Linux_*.xml is unrelated,
> it is simply telling you libreoffice cannot find a JRE (but it will work
> fine without it, for the most part).
>
> What you're seeing is apparmor confinement finally working as intended. The
> package had been shipping apparmor profiles for some time, but they were not
> functional, and they have been fixed.
> Those profiles allow reading/writing office documents in $HOME, /mnt and
> /media (that excludes /home2/).
>
> Can you try running the following command in a terminal, and confirm
> that this "fixes" your issue:
>
> sudo apparmor_parser -R
> /etc/apparmor.d/usr.lib.libreoffice.program.*
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1751005 [1]
>
> Title:
> libreoffice cannot open a document not within $HOME
>
> Status in libreoffice package in Ubuntu:
> New
>
> Bug description:
> Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1),
> files not within the user $HOME directory cannot be opened. This has
> nothing to do with ownership or permissions - the target document is
> owned by the user with full permissions. Moving the file to ~/Desktop
> allows it to be opened normally.
>
> Error message in popup window:
> Access to /home2/mico/documents/personal/2018 lists.ods was denied.
>
> Error message when launched from terminal:
> $: localc "2018 lists.ods"
> javaldx: Could not find a Java Runtime Environment!
> Please ensure that a JVM and the package libreoffice-java-common is installed.
> If it is already installed then try removing
> ~/.libreoffice/3/user/config/javasettings_Linux_*.xml
> Warning: failed to read path from javaldx
>
> The file mentioned in the error message does not exist.
> I removed the corresponding file under ~/.libreoffice/4/ but that makes no
> difference.
>
> This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with
> today's update (Feb. 22) it appeared in Ubuntu 17.10.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1
> ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
> Uname: Linux 4.13.0-36-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Thu Feb 22 09:35:49 2018
> InstallationDate: Installed on 2018-01-27 (25 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
> SourcePackage: libreoffice
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions
> [2]
Links:
--
[1] https://bugs.launchpad.net/bugs/1751005
[2]
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not within $HOME
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] [NEW] libreoffice cannot open a document not within $HOME
Public bug reported: Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1), files not within the user $HOME directory cannot be opened. This has nothing to do with ownership or permissions - the target document is owned by the user with full permissions. Moving the file to ~/Desktop allows it to be opened normally. Error message in popup window: Access to /home2/mico/documents/personal/2018 lists.ods was denied. Error message when launched from terminal: $: localc "2018 lists.ods" javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.libreoffice/3/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx The file mentioned in the error message does not exist. I removed the corresponding file under ~/.libreoffice/4/ but that makes no difference. This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with today's update (Feb. 22) it appeared in Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 09:35:49 2018 InstallationDate: Installed on 2018-01-27 (25 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602035] Re: Maps app no longer works because MapQuest disabled access
Broad discussion of gnome maps and libchamplain: https://bugzilla.gnome.org/show_bug.cgi?id=769352 [7] I could not figure out whether my request is already one of the options being considered or even planned. I filed a bug anyway: https://bugzilla.gnome.org/show_bug.cgi?id=769559 [8] On 05.08.2016 14:38, Jeremy Bicha wrote: > Mike, could you file a bug with GNOME directly about that issue against > the libchamplain package? See > https://wiki.ubuntu.com/Bugs/Upstream/GNOME [1] > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1602035 [2] > > Title: > Maps app no longer works because MapQuest disabled access > > Status in Gnome Maps: > Fix Released > Status in Ubuntu GNOME: > Triaged > Status in gnome-maps package in Ubuntu: > Fix Committed > Status in livecd-rootfs package in Ubuntu: > Invalid > Status in ubuntu-gnome-meta package in Ubuntu: > Fix Released > Status in gnome-maps source package in Trusty: > Triaged > Status in gnome-maps source package in Wily: > Won't Fix > Status in gnome-maps source package in Xenial: > Fix Committed > Status in livecd-rootfs source package in Xenial: > Fix Released > Status in ubuntu-gnome-meta source package in Xenial: > Fix Released > Status in gnome-maps package in Debian: > Fix Released > Status in gnome-maps package in Fedora: > Unknown > > Bug description: > As of today, MapQuest has disabled their free map tile feed. This > means the Maps app no longer displays anything except a warning > pointing to > > http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest- [3] > results-in-changes-to-open-tile-access/ > > Screenshot attached. > > [Impact] > GNOME Maps is included by default in Ubuntu GNOME 15.10 and 16.04. The app > currently is useless. > > Triaged as "High" because it "prevents the application or any > dependencies from functioning correctly at all". > https://wiki.ubuntu.com/Bugs/Importance [4] > > This also breaks libchamplain (a library for embedding maps into your > app). Once a fix is released, apps using libchamplain will likely need > to be patched to use a different map provider. > > [Test Case] > Install gnome-maps. Open the Maps app. Do you see maps? > > Note that maps are cached so you may not notice the feed has been > disabled unless you try viewing a specific area at a close enough zoom > that you have not viewed recently. > > [Regression Potential] > Upstream changes to switch to Mapbox has potential to break unrelated > features. > > https://mail.gnome.org/archives/desktop-devel- [5] > list/2016-July/msg3.html > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions [6] Links: -- [1] https://wiki.ubuntu.com/Bugs/Upstream/GNOME [2] https://bugs.launchpad.net/bugs/1602035 [3] http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest- [4] https://wiki.ubuntu.com/Bugs/Importance [5] https://mail.gnome.org/archives/desktop-devel- [6] https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions [7] https://bugzilla.gnome.org/show_bug.cgi?id=769352 [8] https://bugzilla.gnome.org/show_bug.cgi?id=769559 ** Bug watch added: GNOME Bug Tracker #769352 https://bugzilla.gnome.org/show_bug.cgi?id=769352 ** Bug watch added: GNOME Bug Tracker #769559 https://bugzilla.gnome.org/show_bug.cgi?id=769559 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602035 Title: Maps app no longer works because MapQuest disabled access To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1602035] Re: Maps app no longer works because MapQuest disabled access
Thanks. I understand. I was hoping for a way to specify a license key for libchamplain to use. Otherwise I have to write code to replace the functionality of libchamplain. regards Mike On 04.08.2016 19:36, Jeremy Bicha wrote: > Mike, I split the libchamplain part of this bug off to bug 1608308. It > needs to be coordinated upstream since gnome-maps has an agreement with > Mapbox but I don't think it's been asked yet if that agreement will > extend to other core GNOME apps, nor has it been decided whether Mapbox > support will be included in libchamplain if it will be used by multiple > GNOME apps. Third-party apps will need to make their own agreement with > Mapbox or another provider. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1602035 [1] > > Title: > Maps app no longer works because MapQuest disabled access > > Status in Gnome Maps: > Fix Released > Status in Ubuntu GNOME: > Triaged > Status in gnome-maps package in Ubuntu: > Fix Committed > Status in livecd-rootfs package in Ubuntu: > Invalid > Status in ubuntu-gnome-meta package in Ubuntu: > Fix Released > Status in gnome-maps source package in Trusty: > Triaged > Status in gnome-maps source package in Wily: > Won't Fix > Status in gnome-maps source package in Xenial: > Fix Committed > Status in livecd-rootfs source package in Xenial: > Fix Released > Status in ubuntu-gnome-meta source package in Xenial: > Fix Released > Status in gnome-maps package in Debian: > Fix Released > Status in gnome-maps package in Fedora: > Unknown > > Bug description: > As of today, MapQuest has disabled their free map tile feed. This > means the Maps app no longer displays anything except a warning > pointing to > > http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest- [2] > results-in-changes-to-open-tile-access/ > > Screenshot attached. > > [Impact] > GNOME Maps is included by default in Ubuntu GNOME 15.10 and 16.04. The app > currently is useless. > > Triaged as "High" because it "prevents the application or any > dependencies from functioning correctly at all". > https://wiki.ubuntu.com/Bugs/Importance [3] > > This also breaks libchamplain (a library for embedding maps into your > app). Once a fix is released, apps using libchamplain will likely need > to be patched to use a different map provider. > > [Test Case] > Install gnome-maps. Open the Maps app. Do you see maps? > > Note that maps are cached so you may not notice the feed has been > disabled unless you try viewing a specific area at a close enough zoom > that you have not viewed recently. > > [Regression Potential] > Upstream changes to switch to Mapbox has potential to break unrelated > features. > > https://mail.gnome.org/archives/desktop-devel- [4] > list/2016-July/msg3.html > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions [5] Links: -- [1] https://bugs.launchpad.net/bugs/1602035 [2] http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest- [3] https://wiki.ubuntu.com/Bugs/Importance [4] https://mail.gnome.org/archives/desktop-devel- [5] https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602035 Title: Maps app no longer works because MapQuest disabled access To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602035] Re: Maps app no longer works because MapQuest disabled access
I tested 3.18.3 and it seems to work fine. I did not notice any gray space on the right. I ask if libchamplain will now have mapbox as a tile source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602035 Title: Maps app no longer works because MapQuest disabled access To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-maps/+bug/1602035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570198] Re: fotoxx crashes when saving a large tiff to disk
This version of Fotoxx is long obsolete. The current version is available at www.kornelix.com. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570198 Title: fotoxx crashes when saving a large tiff to disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fotoxx/+bug/570198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302546] Re: gtk drawing area - missing or incorrect expose or draw event
This bug should be closed. Fixed in a later release of GTK (see above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302546 Title: gtk drawing area - missing or incorrect expose or draw event To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1302546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336808] Re: old version of Fotoxx in repositories is mislabeled as current version
"confirmed" and "unassigned" apparently forever. Cool system you have here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336808 Title: old version of Fotoxx in repositories is mislabeled as current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fotoxx/+bug/1336808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 863243] Re: fotoxx crashed with SIGFPE in g_cclosure_marshal_VOID__VOID()
This version of Fotoxx (10.7) is long obsolete. The current version is available at www.kornelix.com. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/863243 Title: fotoxx crashed with SIGFPE in g_cclosure_marshal_VOID__VOID() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fotoxx/+bug/863243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507119] Re: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24
I updated the BIOS and the problem seems to have gone away. I rebooted 10 times with no failures. PC has been running over one day with no kernel or other crashes. It looks like this was entirely my problem (and ASRock's buggy BIOS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507119 Title: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509781] [NEW] may relate to bug 1507119
Public bug reported: I was running under kernel 4.3 as requested (see bug 1507119) I got the 4.3 kernel oops and then rebooted to stock kernel 4.2 in order to file a bug report (as requested). However, the reboot to kernel 4.2 triggered a mass of >10 popup windows announcing a bug. This is one of them. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mico 1623 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 25 11:19:02 2015 HibernationDevice: RESUME=UUID=9db24c89-293c-49f8-a46a-90bdd7272e64 InstallationDate: Installed on 2015-10-22 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=/dev/sda8 ro quiet RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd08/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509781 Title: may relate to bug 1507119 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1509781] Re: may relate to bug 1507119
I updated the BIOS to version 1.30. I am now running the 15.10 stock kernel 4.2. I will let you know if the problem still happens, or if there are no crashes after a day or more of operation. I appreciate your help. On 25.10.2015 13:33, Christopher M. Penalver wrote: > Mike Cornelison, thank you for reporting this and helping make Ubuntu > better. > > As per http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming- [1] > ITXac/?cat=Download=BIOS an update to your computer's buggy and > outdated BIOS is available (1.20). If you update to this following > https://help.ubuntu.com/community/BIOSUpdate [2] does it change anything? > > If it doesn't, could you please both specify what happened, and provide the > output of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette [3] > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. As well, you don't > have to create a new bug report. > > Once the BIOS is updated, if the problem is still reproducible, and the > information above is provided, then please mark this report Status > Confirmed. Otherwise, please mark this as Invalid. > > Thank you for your understanding. > > ** Tags added: bios-outdated-1.20 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Low > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Summary changed: > > - may relate to bug 1507119 > + kernel oops > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1509781 [4] > > Title: > kernel oops > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I was running under kernel 4.3 as requested (see bug 1507119) > > I got the 4.3 kernel oops and then rebooted to stock kernel 4.2 > in order to file a bug report (as requested). > > However, the reboot to kernel 4.2 triggered a mass of >10 popup > windows announcing a bug. This is one of them. > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: > boot/vmlinuz-4.2.0-16-generic] > ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 > Uname: Linux 4.2.0-16-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.19.1-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: mico 1623 F pulseaudio > CurrentDesktop: Unity > Date: Sun Oct 25 11:19:02 2015 > HibernationDevice: RESUME=UUID=9db24c89-293c-49f8-a46a-90bdd7272e64 > InstallationDate: Installed on 2015-10-22 (2 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) > MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=/dev/sda8 > ro quiet > RelatedPackageVersions: > linux-restricted-modules-4.2.0-16-generic N/A > linux-backports-modules-4.2.0-16-generic N/A > linux-firmware 1.149 > SourcePackage: linux > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/18/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P1.00 > dmi.board.name: Z170 Gaming-ITX/ac > dmi.board.vendor: ASRock > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: To Be Filled By O.E.M. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd08/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.name: To Be Filled By O.E.M. > dmi.product.version: To Be Filled By O.E.M. > dmi.sys.vendor: To Be Filled By O.E.M. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509781/+subscriptions > [5] Links: -- [1] http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming- [2] https://help.ubuntu.com/community/BIOSUpdate [3] https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette [4] https://bugs.launchpad.net/bugs/1509781 [5] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509781/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509781 Title: kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507119] Re: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24
Not clear what you mean. Do you mean that when I get a kernel oops using the (future) 4.3 kernel, I should reboot to the Ubuntu normal (4.2) kernel to file the bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507119 Title: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507119] Re: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24
I installed the kernel 4.3.0-040300rc6-generic x86_64 The system froze within an hour of rebooting. After reboot, the following error was reported (in >10 separate popup windows) BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 I used the first one (underneath all the others) to send a bug report. I should have mentioned above that I am using a skylake processor. This same computer seems to run fine on Ubuntu 15.04 with stock kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507119 Title: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507119] Re: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24
I tried this and was asked to file the bug upstream to the kernel developers because it is not an Ubuntu package. Do you want me to do this? Related item: I have now seen this same bug: "Bad page state in process xampp-linux-x64 pfn:1b9e24" when using Ubuntu 15.04 with the stock Ubuntu kernel. Now I am wondering if this is related to my use of a skylake processor. I never saw this with my previous haswell processor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507119 Title: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507119] Re: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24
After I installed Ubuntu 15.10 this bug happens frequently, often immediately after boot. The process named is not constant, but appears to be random. BUG: Bad page state in process x This system also has frequent freezes, requiring a reboot. Priority should be "critical" unless only a few persons are getting this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507119 Title: BUG: Bad page state in process xampp-linux-x64 pfn:1b9e24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459557] Re: partitions blacklisted in launcher keep coming back
I characterized this problem more clearly. The culprit is the program gnome-disk-utility. If standby time or APM is set to ON, all partitions of the drive are added to the launcher. If they are removed with unlock from launcher they come back with the next reboot. If the standby time and APM are set to OFF, normal launcher behavior returns. This started happening in May 2015. In my case the disk is /dev/sdb which contains various rarely used Linux partitions (old versions of Ubuntu, Fedora, Suse, Mint) and is normally not spinning (APM set for spin-down). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459557 Title: partitions blacklisted in launcher keep coming back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1459557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459557] [NEW] partitions blacklisted in launcher keep coming back
Public bug reported: Ubuntu 15.04 Problem appeared after using Gparted - not sure if this is related. Symptoms: 1. 10 unmounted partitions are shown in launcher. 2. use unlock from launcher - they go away as they should. 3. log out and log back in - they are still gone as they should be. 4. reboot and log in - they all come back. 5. dconf-editor shows the partitions as blacklisted. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459557 Title: partitions blacklisted in launcher keep coming back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1459557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396361] Re: Double Mouse Cursor
Fotoxx problem does not occur with Ubuntu 15.04 (alpha) as of Jan 26. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396361 Title: Double Mouse Cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1396361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396361] Re: Double Mouse Cursor
Fotoxx double mouse cursor when dragging an image: - problem does not happen on OpenSuse 3.2 with GTK 3.14 - problem does not happen on Ubuntu 14.04 In both cases the same binary executable was used that has this problem in Ubuntu 14.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396361 Title: Double Mouse Cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1396361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396361] Re: Double Mouse Cursor
Fotoxx executable built on Ubuntu 14.10 execute on Ubuntu 14.10: mouse never loses a program-assigned cursor (pixbuf image) mouse accumulates additional cursors whenever assigned execute the same identical binary (without rebuild) on Ubuntu 14.04: no problems, works as it should -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396361 Title: Double Mouse Cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1396361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336808] Re: old version of Fotoxx in repositories is mislabeled as current version
OK, it is confirmed. I guess that is progress. It even seems to be fixed, although unassigned. Now how about just deleting it. The 12.01 version is too old. A current version is available from the Getdeb PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336808 Title: old version of Fotoxx in repositories is mislabeled as current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fotoxx/+bug/1336808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336808] [NEW] old version of Fotoxx in repositories is mislabeled as current version
Public bug reported: Software Center shows Fotoxx 14.07 as available for installation. The content however is the 2.5 year-old version 12.01. Anyone installing this over a more recent version will lose a lot of work. Please delete this now. If you cannot put the current version in the repositories, please just delete it. Mike Cornelison author of Fotoxx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fotoxx 12.01.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 2 16:20:51 2014 InstallationDate: Installed on 2014-04-18 (74 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: fotoxx UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fotoxx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336808 Title: old version of Fotoxx in repositories is mislabeled as current version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fotoxx/+bug/1336808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302546] Re: gtk drawing area - missing or incorrect expose or draw event
I ran a simple experiment to find out if the bug is fixed in a later release of GTK. The answer is YES. I installed gtk 3.12 using the PPAs gnome3-team and ricotz. The bug is gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302546 Title: gtk drawing area - missing or incorrect expose or draw event To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1302546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302546] Re: gtk drawing area - missing or incorrect expose or draw event
Bug report filed with Gnome bugzilla: #727650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302546 Title: gtk drawing area - missing or incorrect expose or draw event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1302546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302546] [NEW] gtk drawing area - missing or incorrect expose or draw event
Public bug reported: Application is Fotoxx 14.04. A GTK notebook is used with tabs containing drawing areas inside scrolled windows. The program works on Ubuntu 13.10 and earlier (GTK 3.8) and fails on Ubuntu 14.04 beta (as of April 4) (GTK 3.10). When the notebook tab is changed the new tab's drawing area is not updated (Fotoxx gallery page). Some prior data is present and the rest is background color only. Clicking elsewhere and then clicking the window title bar (unfocus and refocus the app) causes the tab to update correctly. Removing the default double buffered attribute from the drawing area widget after it is created makes everything work correctly on Ubuntu 14.04. However on earlier Ubuntu releases the background is not updated and is filled with data from the previous tab. This seems to be a problem with missing draw events or events with incorrect update regions. I have verified that draw events are not sent when the tab is switched but are sent when the window acquires focus. The GTK bug tracking system seems to have related bugs but I cannot be sure (too much technical jargon for my knowledge of GTK internals). I did not file a report there because the expected knowledge of internals is missing. The bug may be fixed in GTK 3.12. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-0 3.10.7-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 13:28:59 2014 InstallationDate: Installed on 2014-03-28 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302546 Title: gtk drawing area - missing or incorrect expose or draw event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1302546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299100] [NEW] fails to install packages that were OK prior to 14.04
Public bug reported: Ubuntu Software Center exits with this message: The installation or removal of a software package failed. Selecting details in the USC dialog gives the following information: previously unselected package libtiff4:amd64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 168308 files and directories currently installed.) Preparing to unpack .../libtiff4_3.9.7-3ubuntu1_amd64.deb ... Unpacking libtiff4:amd64 (3.9.7-3ubuntu1) ... Selecting previously unselected package libimage-exiftool-perl. Preparing to unpack .../libimage-exiftool-perl_9.46-1_all.deb ... Unpacking libimage-exiftool-perl (9.46-1) ... Processing triggers for man-db (2.6.6-1) ... Setting up libtiff4:amd64 (3.9.7-3ubuntu1) ... Setting up libimage-exiftool-perl (9.46-1) ... Processing triggers for libc-bin (2.19-0ubuntu3) ... I ran software-center from a terminal to get the following output: /usr/share/software-center/softwarecenter/backend/installbackend_impl/aptd.py:764: Warning: Source ID 4688 was not found when attempting to remove it GLib.source_remove(self._progress_signal) /usr/share/software-center/softwarecenter/backend/installbackend_impl/aptd.py:764: Warning: Source ID 4693 was not found when attempting to remove it GLib.source_remove(self._progress_signal) /usr/share/software-center/softwarecenter/ui/gtk3/models/pendingstore.py:64: Warning: Source ID 4694 was not found when attempting to remove it GLib.source_remove(sig) /usr/share/software-center/softwarecenter/ui/gtk3/models/pendingstore.py:64: Warning: Source ID 4695 was not found when attempting to remove it GLib.source_remove(sig) /usr/share/software-center/softwarecenter/ui/gtk3/models/pendingstore.py:64: Warning: Source ID 4696 was not found when attempting to remove it GLib.source_remove(sig) /usr/share/software-center/softwarecenter/ui/gtk3/models/pendingstore.py:64: Warning: Source ID 4697 was not found when attempting to remove it GLib.source_remove(sig) 2014-03-28 09:16:00,410 - softwarecenter.backend - ERROR - error in _on_trans_finished 'Error: Package operation failed The installation or removal of a software package failed. ' 2014-03-28 09:16:04,081 - softwarecenter.db.pkginfo_impl.aptcache - INFO - aptcache.open() 2014-03-28 09:16:05,034 - softwarecenter.utils - WARNING - Could not determine the installed desktop file path for app-install desktop file: '/usr/share/app-install/desktop/fotoxx:kornelix-fotoxx.desktop' 2014-03-28 09:16:05,035 - softwarecenter.backend.zeitgeist_logger - WARNING - Invalid desktop file provided, impossible to log event Additional information: The package being attempted was Fotoxx, available at: www.kornelix.com/packagesand in the GetDeb PPA Both of these fail the same way. The package installs OK in several prior releases of Ubuntu going back to 12.04. The package installs OK using $ sudo dpkg --install fotoxx-14.04-x86_64.deb ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-center 13.10-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 28 17:24:45 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) PackageArchitecture: all SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299100 Title: fails to install packages that were OK prior to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1299100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
