[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
I will prepare an upload of unionfs-fuse that switches to libfuse3 during the next days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Incomplete Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
Hi Christian, I will actually just prepare an upload to debian (via mentors) and then let that get pulled into ubuntu. I don't know what "unionfs-fuse isn't seeded (anymore)" means - automatic pulling from debian is not done anymore or something else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@Paride Thanks for your help and explanations. Yeah I know what multi- arch does although I didn't know about 'Multi-Arch: foreign' - so thank you very much for the pointers. @Christian I have uploaded the updated package to mentors on Sunday. It was prepared on Ubuntu, though, I guess it is better when to redo the steps through a debian chroot - I hope I come to that in the evening. https://mentors.debian.net/package/unionfs-fuse/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069516] Re: Wrong top page margin
** Package changed: cups (Ubuntu) => cups-filters (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1069516 Title: Wrong top page margin Status in “cups-filters” package in Ubuntu: New Bug description: Ever since upgrading to Precide I'm fighting with my printer. Unfortunately, so far I could not track down the exact package - I already tried to downgrade cups, ghostscript, etc to the Debian Squeeze versions (I have a change chroot for that). So every time after rebooting the system somehow the top page marging is increased by 2cm. Setting it to small values in the printers.conf does not help. Running "lpoptions -p FS-1000+ -o page-top=0" in rc.local does not help either. Setting the users values in $HOME/.cups/lpoptions also does not help. Changing values in the PPD file does not seem to have any effect on the top margin. The only solution I found so far is to delete and to re-install the printer from scratch every time after a reboot. Rather annoying, as I don't have a script for that so far. I really would appreciate any suggestions how to fix this annoying problem. Printer is a Kyocera FS-1000+ (pcl only). I also tried several PCL generators (Foomatic, hpijs), it does not change anything about the top-margin problem either. Unless there are other suggestions, I will try to update to the next ubuntu version next week. Thanks, Bernd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1069516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069516] [NEW] Wrong top page margin
Public bug reported: Ever since upgrading to Precide I'm fighting with my printer. Unfortunately, so far I could not track down the exact package - I already tried to downgrade cups, ghostscript, etc to the Debian Squeeze versions (I have a change chroot for that). So every time after rebooting the system somehow the top page marging is increased by 2cm. Setting it to small values in the printers.conf does not help. Running "lpoptions -p FS-1000+ -o page-top=0" in rc.local does not help either. Setting the users values in $HOME/.cups/lpoptions also does not help. Changing values in the PPD file does not seem to have any effect on the top margin. The only solution I found so far is to delete and to re-install the printer from scratch every time after a reboot. Rather annoying, as I don't have a script for that so far. I really would appreciate any suggestions how to fix this annoying problem. Printer is a Kyocera FS-1000+ (pcl only). I also tried several PCL generators (Foomatic, hpijs), it does not change anything about the top-margin problem either. Unless there are other suggestions, I will try to update to the next ubuntu version next week. Thanks, Bernd ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1069516 Title: Wrong top page margin Status in “cups” package in Ubuntu: New Bug description: Ever since upgrading to Precide I'm fighting with my printer. Unfortunately, so far I could not track down the exact package - I already tried to downgrade cups, ghostscript, etc to the Debian Squeeze versions (I have a change chroot for that). So every time after rebooting the system somehow the top page marging is increased by 2cm. Setting it to small values in the printers.conf does not help. Running "lpoptions -p FS-1000+ -o page-top=0" in rc.local does not help either. Setting the users values in $HOME/.cups/lpoptions also does not help. Changing values in the PPD file does not seem to have any effect on the top margin. The only solution I found so far is to delete and to re-install the printer from scratch every time after a reboot. Rather annoying, as I don't have a script for that so far. I really would appreciate any suggestions how to fix this annoying problem. Printer is a Kyocera FS-1000+ (pcl only). I also tried several PCL generators (Foomatic, hpijs), it does not change anything about the top-margin problem either. Unless there are other suggestions, I will try to update to the next ubuntu version next week. Thanks, Bernd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1069516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Stupid question, why should network-manager not be killable? From my point of view everything should be killed before a shutdown except of processes, which are absolutely required to continue the shutdown/reboot. So for example if you are using unionfs-fuse for "/", "/etc" or "/var" and kill its daemon, shutdown cannot continue. But how is that related to the network manager? Assuming there is a network file system involved, kill network-manager or dhclient should not fail the network connection, at least not unless network manager does that. But that would be a in network-manager and should be fixed instead. A simply workaround even would be to kill it with SIGTERM to give it no chance to do any harm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I fail to understand why so many people are insisting this is a kernel bug. It isn't. What basically happens is that the network-manager process is not killed by killall5. This process also has an open file descriptor and therefore the root partitions cannot be mounted read-only before shutdown, as the kernel reports it is busy. Network-manager will not be killed due to the ubuntu patch add_sendsigs_omissions.patch, which was added to NM for a similar reason: From: Mathieu Trudel-Lapierre Subject: Move NM's spawns pid files to /run/sendsigs.omit.d. Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/869635 The pidfiles are only used by NM to start and be able to stop the same process, their actual location doesn't overly matter. In this case, putting them under /run/sendsigs.omit.d allows shutdown to skip over those as handled by an upstart job, and in fact they are (although indirectly). I have no idea what Mathieu actually intended with this patch, but it is entirely wrong and made everything worse. Instead of refusing to kill NM, it needs to be killed, which is just the other way around than what the patch is doing. The only way to fix this from kernel point of view would be to write a kernel patch to allow to mount read-only while there are still file descriptors, which have write access. All those FDs would need to be closed from the kernel side and propably would cause application crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Well, network usually does not break by killing dhclient, at least not if the lease does not expire just in this second. If we ignore this race, probably only modem processes are left. But these are not even considered by the add_sendsigs_omissions.patch. The patch only touches nm-dhcp-dhclient.c, nm-dhcp-dhcpcd.c, nm-dns-bind.c and nm-dns-dnsmasq.c. Except for the lease/shutdown race none of these should be required for anything that is already mounted - the kernel nfs client already knows the IP of the server. If we don't want to ignore the lease race and we don't trust NM to kill sub-processes we need a to run killall5 a 2nd time and this time it only must ignore fuse processes. However, if the root file system or /etc or /var are on NFS, we cannot fix this race at all and have to leave it to the admin to provide sufficiently long leases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On 02/18/2013 10:10 AM, Steve Langasek wrote: > On Mon, Feb 18, 2013 at 08:32:14AM -0000, Bernd Schubert wrote: > >> Well, network usually does not break by killing dhclient, > > Irrelevant. The dhclient process is managed by NM, and sendsigs must not > interfere with it. > >> If we don't want to ignore the lease race and we don't trust NM to kill >> sub-processes > > We *require* NM to clean up its subprocesses. This is the only sane > architecture. If NM is not doing so, that's a bug in NM. Well, do as you like, but from my point of view an init system that does not properly kill processes is broken by design. Relying on something is always wrong, especially if it is system critical (I got severe data loss on my btrfs partition due to this bug here). killall5 is there to enfore things, not to rely on them... It is nice that it speeds up shutdown, but that is only a side effect. So far I also only see a patch in NM that made it worse than it had been before. Properly fixing NM is certainly correct, but that still is no enforcement that shutdown properly works. I know how to fix it on my systems and I'm going to publish that information, but other than that I'm giving up on upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On 01/22/2014 05:51 PM, Steve Langasek wrote: > On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: >> Lennert of systemd refers to this bug on google+. He outlines a fix for >> the simple case: > > The fix he outlines is not for this bug. It's not for a bug we have in > upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of > all of upstart's library dependencies, which are finite and accounted for. Why shouldn't switching to an independent file system (tmpfs/initramfs) and shutdown-init-process not help? That way you can kill all processes without exceptions. You can even entirely unmount the old root, no need for remounting it read-only anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329056] Re: lightdm does not start under systemd
Same issue for me on Wily on one of my systems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1329056 Title: lightdm does not start under systemd Status in lightdm package in Ubuntu: Expired Bug description: Lightdm does not start under ssytemd. Starting it by hand works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 Date: Wed Jun 11 21:08:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (356 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2013-11-10 (213 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1329056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
