[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
I have tested the proposed kernel as requested and updated tag to verification-done-bionic. System booted as expected. Thank you for fixing this. ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Thanks You-Sheng, I'll set aside some time shortly to upgrade. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Well done You-Sheng! Tried both packages and they worked fine. Don't worry about the delay, I have more than enough to keep me occupied at the moment. Thanks much for your efforts here. What happens next, just wait for 20.04.1 to release? Do I need to clean anything up or can I just leave as is for the moment? Regards. Tony -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello yet again You-Sheng, OK, I'm missing something here unfortunately. I've dome the first clone:- git clone -b bug-1856387/fix-PIT-skip/bionic https://git.launchpad.net/~vicamo/+git/ubuntu-kernel but obviously the second will be a problem trying to clone into 'ubuntu-kernel'. What is:- git clone -b bug-1856387/fix-PIT-skip/bionic git+ssh://tony-buck...@git.launchpad.net/~vicamo/+git/ubuntu-kernel Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello again You-Sheng, I think I get something. I think I understand what you mean by it would take several hours to publish built binaries. You want me to follow those links on the ppa page and do those git clones? I'm doing that anyway just see what happens. Regards. Tony -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, (hope you are well by the way) I've applied your ppa as described sudo add-apt-repository ppa:vicamo/ppa-1856387 sudo apt-get update However I'm not sure what to do next. I assume it installed some packages, but how do I test. I tried a reboot, but I couldn't see how it would work as the latest kernel I have available is 4.15.0-99 and I understand the changes are in the 5... kernels. Do I need to get or build a new kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
OK. I must confess I'm a bit vague on ppa's. Does it clone the kernel source and then I do a build and test? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, I've only just noticed this. Thanks for responding. I've been a bit busy lately, but I'll either try one of the bionic 5.3 kernels or try your ppa test hopefully soon. Thanks. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello all, Does anyone know if this bug will cause a problem upgrading to Ubuntu 20.04 LTS? I assume it will as we're stuck using an older kernel and 20.04 is based on kernel 5.4. Or, will it simply upgrade and keep us on the older kernel? Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
I have tested a proposed patch by Thomas Gleixner (t...@linutronix.de) at both the identified commit and also at the latest version and in both cases my computer booted successfully. Comment also posted in bugzilla. https://bugzilla.kernel.org/show_bug.cgi?id=206125 Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Thanks for your feedback, You-Sheng. I've added a comment to that effect now. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
I have filed a bug in bugzilla. Hopefully it's been done OK as I've not done this before. It is as follows:- Bug 206125 - Freezing on boot since kernel 4.15.0-72-generic release Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hi You-Sheng, Thanks for responding. Sadly, the problem is not fixed in v5.5-rc5 mainline kernel. I'll look at lodging a bug in bugzilla. Also I'll try putting some debug code around in that commit to see if I can identify anything. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello again, sorry I meant to add the git bisect log (FYI). See below:- # bad: [48d6312566e04b7a713cc7c15ae7dcd37efcfa95] UBUNTU: Ubuntu-4.15.0-72.81 # good: [ad85666cf30fb921558424a18cabbf396361a90c] UBUNTU: Ubuntu-4.15.0-70.79 git bisect start 'Ubuntu-4.15.0-72.81' 'Ubuntu-4.15.0-70.79' # good: [c76da031386f02b6738e6ba9a132dc3b817e8ba4] arm64: ssbs: Don't treat CPUs with SSBS as unaffected by SSB git bisect good c76da031386f02b6738e6ba9a132dc3b817e8ba4 # bad: [4e160cf6dea3a8521bb8488532f18c69868622cf] mlxsw: spectrum: Set LAG port collector only when active git bisect bad 4e160cf6dea3a8521bb8488532f18c69868622cf # good: [7adb99a811f00df95c29751a0e77ffab97c96fd1] selftests: lib.mk set KSFT_TAP_LEVEL to prevent nested TAP headers git bisect good 7adb99a811f00df95c29751a0e77ffab97c96fd1 # good: [b04e95663b835ee0e34d64ce9a6178b083b788ff] net: ena: remove inline keyword from functions in *.c git bisect good b04e95663b835ee0e34d64ce9a6178b083b788ff # bad: [4d4aa7f60b63e5b5477e2b3536633b4c28ef5f65] dm snapshot: rework COW throttling to fix deadlock git bisect bad 4d4aa7f60b63e5b5477e2b3536633b4c28ef5f65 # good: [069a7c0f0d8cba118849543a4fc72384d3679fd6] UBUNTU: [Packaging] dkms -- dkms-build quieten wget verbiage git bisect good 069a7c0f0d8cba118849543a4fc72384d3679fd6 # bad: [46888ff0dc436827f5fdfb0a77d7f50845f154ab] thermal: int340x: processor_thermal: Add GeminiLake support git bisect bad 46888ff0dc436827f5fdfb0a77d7f50845f154ab # bad: [f723dd269d0740e09af47bb5590ffc4f61766153] x86/timer: Skip PIT initialization on modern chipsets git bisect bad f723dd269d0740e09af47bb5590ffc4f61766153 # good: [f25dc28338aa6277fa1e832416802c83bf8ed4e2] efi: efi_get_memory_map -- increase map headroom git bisect good f25dc28338aa6277fa1e832416802c83bf8ed4e2 # first bad commit: [f723dd269d0740e09af47bb5590ffc4f61766153] x86/timer: Skip PIT initialization on modern chipsets -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello, I have completed the bisect as requested and identified the problem commit. The bisect message is as follows:- git bisect good f723dd269d0740e09af47bb5590ffc4f61766153 is the first bad commit commit f723dd269d0740e09af47bb5590ffc4f61766153 Author: Thomas Gleixner Date: Thu Nov 7 09:05:00 2019 +0100 x86/timer: Skip PIT initialization on modern chipsets BugLink: https://bugs.launchpad.net/bugs/1851216 Recent Intel chipsets including Skylake and ApolloLake have a special ITSSPRC register which allows the 8254 PIT to be gated. When gated, the 8254 registers can still be programmed as normal, but there are no IRQ0 timer interrupts. Some products such as the Connex L1430 and exone go Rugged E11 use this register to ship with the PIT gated by default. This causes Linux to fail to boot: Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. The panic happens before the framebuffer is initialized, so to the user, it appears as an early boot hang on a black screen. Affected products typically have a BIOS option that can be used to enable the 8254 and make Linux work (Chipset -> South Cluster Configuration -> Miscellaneous Configuration -> 8254 Clock Gating), however it would be best to make Linux support the no-8254 case. Modern sytems allow to discover the TSC and local APIC timer frequencies, so the calibration against the PIT is not required. These systems have always running timers and the local APIC timer works also in deep power states. So the setup of the PIT including the IO-APIC timer interrupt delivery checks are a pointless exercise. Skip the PIT setup and the IO-APIC timer interrupt checks on these systems, which avoids the panic caused by non ticking PITs and also speeds up the boot process. Thanks to Daniel for providing the changelog, initial analysis of the problem and testing against a variety of machines. Reported-by: Daniel Drake Signed-off-by: Thomas Gleixner Tested-by: Daniel Drake Cc: b...@alien8.de Cc: h...@zytor.com Cc: li...@endlessm.com Cc: rafael.j.wyso...@intel.com Cc: hdego...@redhat.com Link: https://lkml.kernel.org/r/20190628072307.24678-1-dr...@endlessm.com (backported from commit c8c4076723daca08bf35ccd68f22ea1c6219e207) Signed-off-by: You-Sheng Yang Acked-by: Stefan Bader Acked-by: Connor Kuehl Signed-off-by: Stefan Bader :04 04 9c51f067713006f928684555c3254e89bdc10361 ad4d7a34eed39a733c78e630f4d9125f67e001bb M arch Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, Thanks for responding again. Yes, I was just looking at doing a bisect. I've done it before for another problem. I just have to familiarise myself again with the procedures for it. Will attend to it soon. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello, Just updating to say that I tried the upstream kernel below but the problem is still present. Upstream kernel: 5.5.0-050500rc1-generic Regards. Tony -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hello You-Sheng, Thanks for responding. I tried "hpet=disable" on a boot for both -70 and -72. No change. Kernel -72 still just stops, but -70 boots OK. As for the dmesg, I don't seem to be able to get any logging / messaging for -72. The only reference I can find for it is in the dpkg log when it was installed back on 4-Dec-2019. It's as if it does not even start. For what it's worth I've attached the dmesg for the -70 boot with "hpet=disable". ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+attachment/5312469/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856387] [NEW] Freezing on boot since kernel 4.15.0-72-generic release
Public bug reported: After the update to install kernel 4.15.0-72-generic (a bit over a week ago) my computer will not boot. On boot, all I see is the purple screen with: Loading Linux 4.15.0-72-generic ... Loading initial ramdisk ... and nothing happens. Just sits there. I've waited about 5-10 minutes on occasion but to no avail. I've checked a number of logs in /var/log but not found anything. If I go into the advanced options and select kernel 4.15.0-70-generic, the computer boots normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 21:53:14 2019 HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1 InstallationDate: Installed on 2018-09-16 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE Sabre 17WV8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F05 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sabre 17WV8 dmi.board.vendor: GIGABYTE dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A: dmi.product.family: Sabre dmi.product.name: Sabre 17WV8 dmi.product.version: Not Applicable dmi.sys.vendor: GIGABYTE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Just upgraded to 18.04.03 and thought I'd check if there was any action on this, but alas, no change. I see you were asking for a journalctl dump. Here's mine from today attached. H/W & driver details are:- *-display UNCLAIMED description: VGA compatible controller product: GP106M [GeForce GTX 1060 Mobile] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list configuration: latency=0 resources: memory:a300-a3ff memory:9000-9fff memory:a000-a1ff ioport:4000(size=128) memory:a400-a407 *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:28 memory:a200-a2ff memory:8000-8fff ioport:5000(size=64) memory:c-d Hopefully this is what you are after. Regards ** Attachment added: "jnlctl.hdmi" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+attachment/5284421/+files/jnlctl.hdmi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1816032] Re: gtk_widget_destroy reports error
It certainly does look related and absolutely agree that its not really a high priority. Thanks. Regards. On 19/2/19 2:20 am, Sebastien Bacher wrote: > Looking upstream it seems similar to > https://gitlab.gnome.org/GNOME/gtk/issues/125 , the warning is indeed > fixed in the current Ubuntu serie, could be a candidate to include if we > do a SRU update for gtk but doesn't seem an high importance one/probably > not worth an update by itself > > > ** Package changed: libcanberra (Ubuntu) => gtk+3.0 (Ubuntu) > > ** Changed in: gtk+3.0 (Ubuntu) > Status: Incomplete => Fix Released > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1816032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816032] Re: gtk_widget_destroy reports error
The original package noted was a mistake. The nearest I can guess at for this problem is as above. I couldn't find anything that was obvious for a problem Gtk+3.0 development ** Package changed: ubuntu => libcanberra (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816032] Re: gtk_widget_destroy reports error
** Package changed: network-manager-applet (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1816032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816032] Re: gtk_widget_destroy reports error
Apologies for the mess up. I was looking at a similar bug listed for the network applet. I thought I had changed it, but the first time I tried to save I had a timeout and had to re-enter the details all over. Somehow the network applet must have been set when I re-entered. It was meant to a problem with Gtk+3.0 Dev. Sample code to reproduced is attached. ** Attachment added: "test_cbox_destroy.c" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+attachment/5239013/+files/test_cbox_destroy.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1816032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816032] [NEW] gtk_widget_destroy reports error
Public bug reported: I have recently installed Ubuntu 18.04 on a new computer and have a Gtk+3.0 program that reports an error:- Gtk-CRITICAL gtk_widget_is_drawable: assertion 'GTK_IS_WIDGET (widget)' failed The same program runs without error on another computer with 16.04. The problem occurs when a ComboBoxText widget in a container (grid) is destroyed using gtk_widget_destroy. Other widgets may be affected but the problem does not occur for GtkScale widgets. The widget does actually get destroyed, but the message is produced in the process. I have also found that using gtk_container_remove avoids the error, but the docs indicate that this is inefficient and not preferred. I have attached a test program to reproduce the error. It also includes a few other things that I tried to see if they made any difference but to no avail. 'Destroy cbox' is the essential test to reproduce. System details: Description:Ubuntu 18.04.1 LTS Release:18.04 libwxgtk3.0-dev: Installed: (none) Candidate: 3.0.4+dfsg-3 Version table: 3.0.4+dfsg-3 500 500 http://au.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: destroy gtk widget -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816032 Title: gtk_widget_destroy reports error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1816032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Thought I'd add my 2 cents worth. I only just tried adding a second monitor in addition to my laptop a few days ago and had this problem. Tried many of the suggested solutions - none worked. Works OK in windows 10. Also works OK in 16.04. Tried using a HDMI to digital adapter at the monitor - did not work. OK in windows 10. Alas cannot try the adapter at the computer as no digital or dvi plug. xrandr pretty as in others shown above - HDMI-1 disconnected. Hopefully this will be fixed before too long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after kernel upgrade
Hello Christopher, Sorry for the delay in responding. I've been away. 1. I tested 1.0.4 shortly after release and I can confirm that the problem still persists. The network plug-in in the package (iscan-network-nt) that I am fairly sure is the problem has not been changed since 2013. This plug-in is proprietary and we don't have source code (that I can find anyway). 2. My interactions with Epson support bordered on being comical. I first contacted them shortly after I noticed the problem on the off chance they may have had some input. The response was that they do not support Linux and simply provided a link to the driver download page. I next contacted them when I was pretty sure what the problem was, explaining that I understood there was no Linux support, but that I didn't want support as such. I explained in general terms what was happening, what needed to be done and that I was trying to trace the origins / ownership of the network plug-in or could they follow it up. The response I received was that they are very supportive of Linux and then proceeded to tell me all the options for "printing" under Linux and that my best option was to use GIMP! When I responded (politely) that nowhere in my mail did I mention printing, but that I had mentioned a scanner problem several times, they responded that they thought I should contact my computer support - Linux! So, in effect, I got nowhere. At least I have a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600753] Re: System Settings missing icons
Hello, What I ended up doing was a bit ham-fisted I'm afraid. My user has its own 'bin' directory which I like to keep at the top of the PATH, so I created an overriding shell script to set the XDG_CURRENT_DESKTOP variable and then call the system command thus: cat gnome-control-center #!/bin/sh # A frontend to the system 'gnome-control-center' to set the # XDG_CURRENT_DESKTOP variable to GNOME. This ensures all icons appear. # A bug has been logged for this issue. # Only applies to xubuntu sessions if [ "$DESKTOP_SESSION" = "xubuntu" ] then export XDG_CURRENT_DESKTOP=GNOME fi /usr/bin/gnome-control-center exit 0 You could rename /usr/bin/gnome-control-center and then call that in an override /usr/bin/gnome-control-center script as above in /usr/bin I suppose, but I'd be a bit wary of this. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600753 Title: System Settings missing icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1600753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after kernel upgrade
There have been some developments with this problem so I thought I should post the latest news. Firstly, I have reported the problem as directed above to the people concerned and the netdev team twice, but there has been no response. Secondly, I managed to narrow down the cause of the problem in the codeline only to then discover that its a known issue. A suggested patch to fix the problem was rejected with the expectation that applications would have to be changed to handle the new kernel network code. Further details may be viewed here:- https://patchwork.ozlabs.org/patch/618164/ No doubt the sentiments expressed in the post are valid, but they seem rather inflexible and harsh to me given that the failing applications were working. Ultimately if an application is not changed, users will be stuck. In my case its no network scanner. Seems crazy to me when a simple change will resolve the problem. The application in point here (bug 1613027) is the Epson network plugin. Unfortunately Epson or the authoring 3rd party do not publish the source code and my efforts through Epson support to try to raise the issue or trace the origin of the network plugin have been fruitless. So for anyone experiencing the problem here, and it looks like there is at least one, what to do... 1. Do nothing and only have a usb scanner. 2. Download the Linux kernel source code every time there is a new release and apply the suggested patch yourself. 3. Override the system 'listen' function with 'dlsym' whenever the network plugin is invoked. This is what I have done. To this end I have created a repository on my git home page here:- https://github.com/mr-headwind/ListenOverride This should only be viewed as a temporary workaround, but given the circumstances I suspect it may be permanent. Regards. Tony -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
4.9-rc4 is now the latest. Problem not fixed. Regards. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags removed: kernel-bug-exists-upstream-4.8-rc5 ** Tags added: kernel-bug-exists-upstream-4.9-rc4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Sorry just to elaborate on what I did for the above in case its unclear. git checkout master git bisect start git bisect bad v4.4-rc1 git bisect good v4.3 NB. - I built kernels for each of these to confirm the bad / good status of each beforehand. Then ran built kernels, then ran git bisect good / bad as required until completion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
OK, after all my problems trying bisect (see previous comments) I've finally managed to successfully complete one. See the attached bisect log for details of the last good commit (10cbc8f179177c1a6d5f56a46ebddc8f602ce5ac) and the first bad one (ef547f2ac16bd9d77a780a0e7c70857e69e8f23f). Quite a job to muddle through. Hopefully its been worth it. Regards. Tony ** Attachment added: "git_bisect.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+attachment/4766210/+files/git_bisect.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
** Tags removed: needs-bisect ** Tags added: bisect-done ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Just set status back - thought of something else to try. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Apologies in advance for marking this as confirmed, but I'm pretty much out of options. I tried to bisect using mainline kernels (above), but got nowhere. I followed the instructions as given:- git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout 49f9ae92af54217fd9821a7613342178893a72af (NB also tried v4.3.6 and more) This commit was from the last known build where I had no problem - v4.3.6 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3.6-wily) and got this error:- fatal: reference is not a tree: 49f9ae92af54217fd9821a7613342178893a72af I've tried lots of searching to try resolve my bisect issues, but its been of limited help. So I'm really stumped and can't proceed with anything, which is disappointing because I'd really like scanner back. Regards. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Well after many days and heaven alone knows how many hours, I'm beginning to go completely loopy. After getting a number of odd messages (as in above) I finally got the following: debian/rules.d/4-checks.mk:12: recipe for target 'module-check-generic' failed make: *** [module-check-generic] Error 1 I tried a number of things like adjusting the HEAD, but nothing changed. So I figured I must have made a mistake somewhere and started again. More odd messages. Not wanting to go down that path again I tried playing a little with the bisect range, but all this showed was what I've always suspected - the problem lies between 4.3.0-7.18 and 4.4.0-1.15. When I try to bisect these to confirm, the 'debian.master' directory gets deleted, which appears to be because they are non-linear (whatever that means). Looking at the instructions, they get pretty vague here. Seems to me they are fine for straightforward things, but quite esoteric when things go awry. Is it telling me that I now need to commit bisect the mainline kernels? It mentions something about mapping one to the other, but this proved confusing and useless. I'd like some confirmation about this as all I really know where mainline kernels are concerned is that I have no problem at v4.3.6 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3.6-wily) and have a problem at v4.4-rc1+cod1 (http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.4-rc1+cod1-wily). To be honest, I'm not even sure that posting here is the proper way to seek assistance (I'm starting to suspect it isn't in which case I'm really lost), but will attempt the mainline bisect if I here nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
I need a little assistance - anyone. I've managed to get started (I think) and test the first bisect and tried to mark as 'GOOD', but got the following: git bisect good Bisecting: 147 revisions left to test after this (roughly 7 steps) error: Your local changes to the following files would be overwritten by checkout: debian.master/changelog Please, commit your changes or stash them before you can switch branches. Aborting What is the correct action, there's nothing in the guide about this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Hello Christopher, Just to clear what you require here. I'm a little confused. I've been thru the Mainline builds and established where I'm having a problem (v4.4...) and not having it (4.3.6-040306-generic). So the next step next is to run 'git clone...', 'git bisect...' and start compiling kernels? Um, I'll give it a go, but I've not done this before. I started looking at 'https://wiki.ubuntu.com/Kernel/KernelBisection', followed (with changes) some of the links and ended up at 'https://launchpad.net/ubuntu/xenial/+source/linux' and followed on into some of the Releases (eg. https://launchpad.net/ubuntu/+source/linux/4.4.0-1.15/+build/8880827). I was (initially) under the impression, you wanted me to test these release kernels to establish where my problem started. However installing packages always failed with dependency errors (for example again with 4.4.0-1.15 'linux-headers-4.4.0-1-generic depends on linux- headers-4.4.0-1'). So I guess this isn't what you need and its the git / compile actions. Could you please confirm? Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
4.8-rc5 was the latest when I checked, so I tested this instead. Problem still exists. ** Tags removed: kernel-bug-exists-upstream-4.8-rc2 ** Tags added: kernel-bug-exists-upstream-4.8-rc5 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Hopefully this will be of assistance, in case anyone looks at this bug. I've run the following commands under the current kernel (4.4.0-34-generic) and also a previous kernel (4.2.0-41-generic) strace scanimage -L log_curr_kernel_not_work 2>&1 Scanner not detected strace scanimage -L log2_prev_kernel_works 2>&1 Scanner works fine Files attached. Diffing the logs shows the interesting stuff at line 3072 (log_curr_kernel_not_work) and line 3232 (log2_prev_kernel_works). It appears that there is an issue connecting under the current kernel that doesn't happen in previous kernels. Why? Beyond me I'm afraid, but its disappointing not to have scanning available now. Any help appreciated. Thanks. ** Attachment added: "log2_prev_kernel_works" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+attachment/4729877/+files/log2_prev_kernel_works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
Second log for above post ** Attachment added: "log_curr_kernel_not_work" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+attachment/4729878/+files/log_curr_kernel_not_work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
May be related to bug #1577137 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577137] Re: saned.service masked and cannot be unmasked
I'm also having the same or similar problem with my Epson WF-3520. Worked find at 15.10, nothing after 16.04 upgrade. I was a little confused about which set up some of the comments described here. Mine is a printer / scanner directly connected to the router and accessed wirelessly. So in theory needing to set up a backend is not required(?). I have also bugged this separately at #1613027. I've also tested a few mainline kernels to see where the problem starts (it appears to be all the 4.4... series). Reverting to an earlier kernel allows scanning to work which may be a temporary work-around. In any case I've tried the solutions raised here, but did not succeed. Tony -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577137 Title: saned.service masked and cannot be unmasked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
OK, I've tested a few of the mainlines (binary chop) and as far as I can tell the last kernel that worked OK was 4.3.6-040306-generic (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3.6-wily/). So it looks to me as if its since the start of the 4.4... series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] Re: Network scanner not detected by xsane after upgrade to 16.04
I've tried the above mainline (http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.8-rc2/) on both 64 bit and 32 bit PC's, but the problem has not been fixed. If I get some time and the kernels are available for download I'll try to identify at exactly what kernel it started. Thanks. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613027] [NEW] Network scanner not detected by xsane after upgrade to 16.04
Public bug reported: Hopefully I'm reporting this in the correct area/group. Sorry if not. After upgrading to 16.04, my scanner is no longer detected by xsane (and other scan apps.) The model is 'Epson WF-3520' multi-function and is connected wirelessly to the network. The problem occurs on all my computers: A Dell 64 bit desktop, An Asus 64 bit laptop, A Medion 32 bit laptop. I've upgraded to the latest software released by the manufacturer on 2 computers, but it makes no difference. Printing works OK and also the scanner is detected if I connect using a USB cable (a second printer is installed though). The problem only occurs using the 'linux-image-4.4.0...' series of kernels. If I boot with any of the previous kernels available, 'linux-image-4.2.0...' or 'linux-image-3.19.0...' everything works OK. I am able to ping the scanner. I've tried a number of suggested fixes from searching around various forums, although many of these relate to 'back-end' scanners connected to a host for network access which is not applicable as mine is connected directly to the network. In any case none have worked. I have tried the following: . Removing all manufacturer software and /usr/sane.d/epkowa.conf . Comment out all entries in the /usr/sane.d/dll (Back-end related) . Comment out all entries in the /usr/sane.d/dll.conf.conf except 'net' and adding 'epkowa' (Back-end related) . Disable the firewall (ufw) . Specifically adding a port to use (1865) (ie. net 192.1... 1865 . Linking the libraries in /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane Other than that I'm at a loss and sticking with older kernels. Regards. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 4520 F pulseaudio /dev/snd/controlC1: tony 4520 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 14 16:37:16 2016 HibernationDevice: RESUME=UUID=762f657a-d174-4173-b09d-52d580c09a91 InstallationDate: Installed on 2013-10-01 (1047 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. N71Jq ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=dea23950-d6b3-498c-abba-a94513b58579 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-30 (14 days ago) dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N71Jq.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N71Jq dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN71Jq.204:bd12/24/2009:svnASUSTeKComputerInc.:pnN71Jq:pvr1.0:rvnASUSTeKComputerInc.:rnN71Jq:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N71Jq dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613027 Title: Network scanner not detected by xsane after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600753] Re: System Settings missing icons
Further to the above... After more searching I've found a bug that is similar (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1353480). If I set XDG_CURRENT_DESKTOP=GNOME instead of XFCE and run gnome-control-center from the command line everything appears, although I get some warnings:- ** (gnome-control-center:3142): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:3142): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) If I unset XDG_CURRENT_DESKTOP, then I can run unity-control-center from the command as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600753 Title: System Settings missing icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1600753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600753] [NEW] System Settings missing icons
Public bug reported: I recently upgraded to Ubuntu 16.04 from 15.10. Due to performance problems I switched from the Unity desktop to XUbuntu. However, when I now go to 'System Settings...' (ie. gnome-control-center) there are many missing icons. I've attached a screen shot showing what I now see when I select 'System Settings...' on the menu. For example if I click on the Date in the top panel and choose 'Time & Date settings...', the control centre opens but there is no icon available to change the settings. If I go back to the Unity desktop, all is OK. When I run from the command line this shows:- gnome-control-center ** (gnome-control-center:6595): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-trqm4lBln3: Connection refused ** (gnome-control-center:6595): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:6595): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) I have tried a number suggestions found online, but to no avail:- sudo apt-get install unity-control-center --reinstall sudo apt-get install gnome-control-center --reinstall sudo apt-get install ubuntu-desktop --reinstall sudo apt-get remove unity-control-center sudo apt-get install unity-control-center sudo apt-get install unity-control-center-signon gnome-control-center-unity sudo apt-get install landscape-client Regards. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "System Settings Xubuntu" https://bugs.launchpad.net/bugs/1600753/+attachment/4698725/+files/Screenshot_xubuntu.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600753 Title: System Settings missing icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1600753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
OK, a little tedious, but I got there (as advised). Using the Release list at 'https://launchpad.net/ubuntu/vivid/+source/linux' I can state that the problem started between 3.16.0-28.38 (3.16.0-28-generic) and 3.18.0-8.9 (3.18.0-8-generic). In order to test the latest 3.16 ... I used the Release list at 'https://launchpad.net/ubuntu/utopic/+source/linux' and I can state that release 3.16.0-44.59 (3.16.0-44-generic) was OK. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
Hello, BTW Thanks for looking at this. I appreciate it. Alas kernel 4.3-rc5 doesn't fix it. Things were a little different though. When I booted rc5, the 'Starting version 219' showed straight away and in a few seconds the screen went blank, the TV tuner powered off and everything hung. I waited a few minutes and then manually powered off. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
Hello, I tried rc6 but it did not work. However, instead of the screen going blank after seeing 'Starting version 219', pages of text kept rolling thru. Looked like it was doing some kind of trace and was looping to me. Tried to find it in /var/log when I rebooted but could find anything that looked like it. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
Hello, sorry it has taken so long to get around to the bios update suggested. I've had a lot on. Anyway, sadly nothing has changed. Certainly worth a try, although I was a little doubtful since I can replicate this on 2 other PC's. Here is the output requested:- sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 1.1.4 12/21/2009 Basically its the same. Start from scratch:- The light on the tuner goes out after the boot starts and the system hangs. When I power down and restart the light is out and will come on again after I see the 'ACPI PCC Probe failed starting version 219' and the system boots. If I disconnect the tuner from scratch before switching on the system boots OK. If I boot with a '3.16...' kernel, no problem. Its only started at '3.19...' kernels. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1480642] Re: systemd-boot
Hello, Sorry I had to leave this for a few days ... Anyway I believe I have discovered where the problem lies. First things first, booting with kernel '3.16.0-43-generic' works OK. The other thing I discovered (latest kernel) is that if my TV tuner is active the system won't boot. The light on the tuner goes out after the boot starts and the system hangs. When I power down and restart the light is out and will come on again after I see the 'ACPI PCC Probe failed starting version 219' and the system boots. If I disconnect the tuner from scratch before switching on the system boots OK with the latest kernel. This also explains why I noticed that it would boot OK after using Windows first as it switches the tuner off on shutdown / restart. So it looks like the problem is with the TV tuner or the driver more likely, but only with the latest kernel. Its a fairly old tuner - DVICO usb (AU version) - and all I did to install it was to download http://www.linuxtv.org/downloads/firmware/dvb-usb-bluebird-01.fw; and copy to /lib/firmware. I use MeTV. Hopefully this helps. Again, any advice / tips much appreciated. Regards. Tony On 04/08/15 02:33, Joseph Salisbury wrote: Will the system boot if you select the previous kernel from the GRUB menu? ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439439/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439441/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439435/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439433/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439443/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439440/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439436/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439434/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439432/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439442/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439444/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439438/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439437/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
apport information ** Tags added: apport-collected ** Description changed: Following advice as per Release Notes (https://wiki.ubuntu.com/VividVervet/ReleaseNotes) Just upgraded from 14.10 to 15.04 and now Ubuntu fails to start from powering up. I select 'ubuntu' on the grub loader screen and then get a blank screen. Computer just hangs. Have tried Ctrl + Alt + 1 etc, and also leaving for several minutes but nothing happens. Once I power down manually and restart and try again I see a message 'ACPI PCC Probe failed, starting version 219' and PC boots OK. This has repeated each time from scratch. FYI lsb_release -rd RegardsDescription:Ubuntu 15.04 Release:15.04 + --- + ApportVersion: 2.17.2-0ubuntu1.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tony 1694 F pulseaudio + /dev/snd/controlC1: tony 1694 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=ecd554d6-6ffc-440b-b184-bfa1268799bf + InstallationDate: Installed on 2014-08-23 (346 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: Dell Inc. Studio XPS 435MT + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=ef670394-9aa8-4c94-8054-cd701afb0a66 ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-25-generic N/A + linux-backports-modules-3.19.0-25-generic N/A + linux-firmware 1.143.2 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: vivid + Uname: Linux 3.19.0-25-generic x86_64 + UpgradeStatus: Upgraded to vivid on 2015-07-22 (13 days ago) + UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/19/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.0.8 + dmi.board.name: 0R849J + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd01/19/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA00:cvnDellInc.:ct3:cvr: + dmi.product.name: Studio XPS 435MT + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439431/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
apport information ** Description changed: Following advice as per Release Notes (https://wiki.ubuntu.com/VividVervet/ReleaseNotes) Just upgraded from 14.10 to 15.04 and now Ubuntu fails to start from powering up. I select 'ubuntu' on the grub loader screen and then get a blank screen. Computer just hangs. Have tried Ctrl + Alt + 1 etc, and also leaving for several minutes but nothing happens. Once I power down manually and restart and try again I see a message 'ACPI PCC Probe failed, starting version 219' and PC boots OK. This has repeated each time from scratch. FYI lsb_release -rd RegardsDescription:Ubuntu 15.04 Release:15.04 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1694 F pulseaudio /dev/snd/controlC1: tony 1694 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ecd554d6-6ffc-440b-b184-bfa1268799bf InstallationDate: Installed on 2014-08-23 (346 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 435MT Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=ef670394-9aa8-4c94-8054-cd701afb0a66 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-07-22 (13 days ago) UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0R849J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd01/19/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 435MT dmi.sys.vendor: Dell Inc. + --- + ApportVersion: 2.17.2-0ubuntu1.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: tony 1694 F pulseaudio + /dev/snd/controlC1: tony 1694 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=ecd554d6-6ffc-440b-b184-bfa1268799bf + InstallationDate: Installed on 2014-08-23 (346 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MachineType: Dell Inc. Studio XPS 435MT + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=ef670394-9aa8-4c94-8054-cd701afb0a66 ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-25-generic N/A + linux-backports-modules-3.19.0-25-generic N/A + linux-firmware 1.143.2 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: vivid + Uname: Linux 3.19.0-25-generic x86_64 + UpgradeStatus: Upgraded to vivid on 2015-07-22 (13 days ago) + UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/19/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.0.8 + dmi.board.name: 0R849J + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd01/19/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA00:cvnDellInc.:ct3:cvr: + dmi.product.name: Studio XPS 435MT + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439445/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439453/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439458/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439449/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439446/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439452/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439451/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439447/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439456/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439457/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439454/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] JournalErrors.txt
apport information ** Attachment added: JournalErrors.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439448/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439450/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1480642/+attachment/4439455/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1480642] Missing required logs.
Greetings, Ran the command as requested (had to install it first). I'm not sure if its worked OK though. Seemed to collect details and clicked 'Send', but lots of error messages / warnings rolled thru on the terminal window. Hopefully OK. Regards. On 03/08/15 20:00, Brad Figg wrote: This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1480642 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1480642] Re: systemd-boot
Hello Joseph, Thanks for responding. Sadly it didn't work either first up. Its very strange because once I go through initial hiccups it boots normally on the latest (and previous - 3.19.0-23-generic) kernels. What is even more crazy (and I'm loath to even say this because it sounds so idiotic) is that it appears to only happen from a completely cold start - as in switch on at the wall switch. These are the steps:- 1. Switch on at wall power (note this also starts my modem and lights up a USB TV tuner I have connected) 2. Switch PC on 3. Select Ubuntu (its a dual boot) and get the hanging problem 4. Power down the PC (holding the PC power switch) 5. Switch PC on again 6. Select Ubuntu and get the 'ACPI PCC Probe failed' message and the PC boots 7. After this I can 'shutdown' or 'restart' with no more problems Another item of interest is that it worked OK if I start up Windows first and then restart - I think. I'll confirm this tomorrow as I've done so many combinations now I'm a little hazy on that one. Regards Tony On 04/08/15 02:33, Joseph Salisbury wrote: Will the system boot if you select the previous kernel from the GRUB menu? ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] Re: systemd-boot
I was initially tempted to put 'systemd' as the package, however, today I tried booting using 'upstart' and the PC still hung. So I've nominated the image as a best guess and because I received an email urging me to nominate a package, but in truth, I'm not sure. Something I have noticed today is that the ... Probe failed ... message did not show. Also the latest update was applied yesterday. Correct image is being used as a 'uname -r' shows '3.19.0-25-generic'. I _can_ get rolling, but any help / pointers would be appreciated. ** Package changed: ubuntu = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1480642] [NEW] systemd-boot
Public bug reported: Following advice as per Release Notes (https://wiki.ubuntu.com/VividVervet/ReleaseNotes) Just upgraded from 14.10 to 15.04 and now Ubuntu fails to start from powering up. I select 'ubuntu' on the grub loader screen and then get a blank screen. Computer just hangs. Have tried Ctrl + Alt + 1 etc, and also leaving for several minutes but nothing happens. Once I power down manually and restart and try again I see a message 'ACPI PCC Probe failed, starting version 219' and PC boots OK. This has repeated each time from scratch. FYI lsb_release -rd RegardsDescription:Ubuntu 15.04 Release:15.04 ** Affects: 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/1480642 Title: systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1480642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242907] Re: The Shutdown button does not work
*** This bug is a duplicate of bug 1242112 *** https://bugs.launchpad.net/bugs/1242112 Hello, I'm a bit doubtful about the cairo-dock link as I do not have it installed. The problem appeared after upgrading from 13.10 to 14.04. The system does shutdown but does not power off. Instead it displays the Ubuntu splash screen with the 5 alternate flashing red dots. I have to then hard power off the pc (it is a laptop). Trying 'sudo shutdown -h now' (also tried -P) did not solve the problem. I've also tried a number of other proposed 'solutions' that I found searching about the problem to no avail. Regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242907 Title: The Shutdown button does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1242907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
