[Bug 1889299] Re: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
This bug happend to me as I had modified my.cnf file instead of puting the modifications in the mysql.conf.d folder. a good reminder to always use the .d directories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889299 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912915] [NEW] grub CLI too difficult to explain to user to recover from failed boot
Public bug reported: Remote machine 100km further away Computer is updating End user thinks computer is slow and pulls the power plug from the computer Turns out computer was updating the kernel Starts machine Grub can't find any kernels anymore and drops into Grub CLI The process of finding the kernel with the CLI is too difficult to explain over the telephone have to drive 100km to the customer location to get Ubuntu to start grub2 needs better failsafes built in. especially with the advent of Internet of Things devices and remote computers. We've all been there, should not be a phrase we are saying about Ubuntu. What needs fixing: Some way of remote access into Grub when it drops into CLI and/or Having grub2 be more highly available and redundant by duplicating the things it needs to start on two area's of the disk. Similar to how GPT works with the partition table at the start and a redundant partition table at the end. and easier commands for the command line. Current way of working grub> ls (hd0,1)(hd0,2)(/dev/mapper/vg/root) grub> set root=(hd0,1) grub> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1 grub> initrd /boot/initrd.img-3.13.0-29-generic grub> boot Proposed way of working grub> boot the command line should only show up when requested. The computer should boot no matter what, even if it has to drop into the previous kernel by itself to do so. Grub2 should be smart enough to search the drives and partitions for a kernel any kernel to get the system up and running. We are in the age of machine learning, yet computers are still not booting for silly reasons. Starting with the bug here. Will consider reporting upstream. ** Affects: grub2 (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/1912915 Title: grub CLI too difficult to explain to user to recover from failed boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912915] Re: grub CLI too difficult to explain to user to recover from failed boot
Here is the machine info from Landscape: Distribution: Ubuntu 18.04.5 LTS (bionic) Hardware: Processor: Intel(R) Celeron(R) CPU N3150 @ 1.60GHz Memory: 8 GiB RAM Storage:Model: SanDisk SDSSDX24 Size: 240 GB Network:Model: Wireless 3160 MAC: f4:06:69:x:x:x IP: 192.168.x.x Model: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller MAC: 1c:1b:0d:x:x:x IP: 192.168.x.x Video: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller Product identifier: GB-BACE-3150 (To be filled by O.E.M.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912915 Title: grub CLI too difficult to explain to user to recover from failed boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
As recommended by the Gnome-shell developers a bug upstream with Mutter is opened. https://gitlab.gnome.org/GNOME/mutter/-/issues/1356 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1356 https://gitlab.gnome.org/GNOME/mutter/-/issues/1356 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Also I'm happy to use a workaround. I'm just a bit disappointed that devilspie no longer works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Thank you for your further input Daniel. The issue is that the stable version of ChromisPOS that I'm using the source code was destroyed by a commit error. I'm working together with the developer providing resources to get the unstable version production ready but that is taking more time than I can afford to wait as gnome-shell's and Ubuntu's development is outpacing what the single developer for ChromisPOS can take on. I'll certainly subscribe to those bugs on remote support. I'll let Zoho also know about these two remote support bugs as they are also working on an internal fix to build into their Zoho Assist SAAS solution, maybe they can assist there too. > I suggest any software that wants a window A to reliably appear over window B > ... I'd prefer to have no dialog boxes at all popping up and have Window A modify itself. Then there is no reliance on the Window Manager at all. :D Thanks again for thinking along on this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Reported this Upstream under https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
This is interesting. When running gnome-shell in Wayland the window placement seems to be correct. I've been testing it a bit. Unfortunately Wayland doesn't allow for remote desktop access so I can't help my customers when something goes wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's bug tracker now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
@Daniel van Vugt Thanks for your understanding and advice. Do you have any recommendations for an alternative window manager that is: - Officially Supported by Canonical under the support contract - Touchscreen Friendly - Secure - Has a sidebar on the left (the product I sell is designed around the Unity design) Gnome is supposed to be the de-facto standard Linux desktop for most distributions. I still don't understand why all these regression bugs are entering Gnome, and the Gnome developers are so hostile to listening to the users and use cases of their desktop. See the gitlab board you pointed me to where the dev, on the subject of the on screen keyboard, just says, nope, I designed it this way, not listening to reason of more than 30 people and then locks the ticket. Even you said "If that's true then this is not a bug." in regards to window placement. Which is just mind boggling, of course it's a bug when the window manager clearly prevents the end user from using the system. There also needs to be an easier way to report things upstream. At the moment everything has to be typed over into a new ticket from Launchpad to Github. Can't there just be some kind of export ticket to GitHub markup? Thanks again for any recommendations on Canonical supported Window Managers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And the cashier side ** Attachment added: "Cashier side of the setup" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
So you can see what the system looks like when installed ** Attachment added: "Opposing Screens Customer" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And before anyone starts anything about freeloading. I donate several thousand euros per year and a lot of my time to open source projects. So, let's not go there. Once again thank you. I hope that it's much clearer now what is not working as expected in Ubuntu 20.04's iteration of Gnome Desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And here is proof that there are no extensions enabled ** Attachment added: "No Extensions enabled" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Some more fun, the onscreen keyboard follows the misplaced dialog box to the non-touchable monitor. ** Attachment added: "Screen Keyboard opens on non touchable area" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394696/+files/Bug1888098_ScreenKeyboardOnNonTouchMonitor.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is an extra treat so you can see why block Caribou is very necessary and the gnome onscreen keyboard implementation makes the system completely unusable. ** Attachment added: "Extra treat why the block caribou extension was on." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394695/+files/Bug1888098_whyGnomeKeyboardIsOff.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so you can see that the Center New Window option does nothing. At least it stopped doing the Easter Egg of putting things halfway between two monitors that's a plus. :D ** Attachment added: "Photo Center new window doesn't do anything" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394694/+files/Bug1888098_CenterNewWindowIgnored.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Thanks for have a new look at this Oh and I forgot to mention this is with the option Center New Windows turned ON in Gnome Tweak Tool Which should theoretically do the same as the DCONF edit line, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so it's easier to understand what the issue is. ** Attachment added: "Photo of the issue faced" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Removing the extensions has the same effect. Block Caribou 36 is necessary as the Point of Sale system (Open source) already has all the buttons and keyboard that are necessary for the use of the Point of Sale system. Yet it contains text entry fields which pop up the on-screen keyboard. There are more touchscreen applications that tablets, such as Kiosks and Point of Sale systems. "gsettings set org.gnome.mutter center-new-windows true" is an easter- egg joke, it puts the windows halfway between the two screens, then stacks them on top of each other. "I think this is probably occurring because the primary display is occupied by a window already. So any more new windows go to the next display that has empty space. If that's true then this is not a bug. And hopefully #3 is good enough." This is a serious bug as the screens are opposing one another. There are two different people with two different information goals looking at each screen. Both screens are occupied by full screen windows. One is the point of sale interface for the cashier and the other is the customer display screen showing the products the customer is purchasing. The expected behavior is to put the window on the same monitor to where the button to open the new window has been pressed. I'll see if I can muster up some screenshots to make it more visual as to what is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888098] [NEW] Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Public bug reported: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888080] [NEW] gnome-tweaks stops USB3.0 video output to DisplayLink screen
Public bug reported: Ubuntu 20.04 LTS gnome-tweaks 3.34.0-2ubuntu1 AOC USB monitor Bus 002 Device 002: ID 17e9:ff10 DisplayLink I1659FWUX What I expected to happen: When the USB3.0 Displaylink monitor is plugged in and gnome-tweaks installed the display remains on and attached as a monitor What happened instead: Installed fresh Ubuntu 20.04 Installed the Displaylink driver Ran the machine for 3 days both the primary display and extended USB display worked fine Installed gnome-tweaks sudo apt install gnome-tweaks the USB3.0 monitor goes black and is removed from the screen settings and xrandr uninstall gnome-tweaks sudo apt purge gnome-tweaks the USB3.0 monitor turns on again and is visible in lsusb and xrandr install gnome-tweaks USB3.0 monitor goes blank and removed from xrandr restart the Displaylink driver sudo systemctl restart displaylink-driver.service screen remains blank and removed from xrandr uninstall gnome tweaks screen turns back on again and everything is back to normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-tweaks 3.34.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 18 21:31:40 2020 InstallationDate: Installed on 2020-07-14 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-tweaks UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-tweaks (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888080 Title: gnome-tweaks stops USB3.0 video output to DisplayLink screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1888080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
There is a workaround via xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1 There needs to be some kind of detection to do this automatically and create a systemD systemctl file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Here is the xinput list-props while the second screen (AOC) is disconnected Here the touch works as expected xinput list-props 11 Device 'Weida Hi-Tech CoolTouch® System': Device Enabled (169): 1 Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix (308): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix Default (309): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Send Events Modes Available (291): 1, 0 libinput Send Events Mode Enabled (292):0, 0 libinput Send Events Mode Enabled Default (293):0, 0 Device Node (294): "/dev/input/event4" Device Product ID (295):9589, 49920 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
There is a regression of this bug in Ubuntu 20.04 using the default Gnome desktop Setup is a Shuttle POS P511 using a Weida CoolTouch controller with driver integrated into the Linux kernel Second screen is a AOC USB-3.1 Display Link monitor without display capabilities only (no touch). When the AOC screen is disconnected the touch works normally. When the AOC screen is connected the touch is out of sync and touches over both screens from the Shutlle/Weida screen. Here is xinput list-props with both screens connected. xinput list-props 11 Device 'Weida Hi-Tech CoolTouch® System': Device Enabled (169): 1 Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix (308): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix Default (309): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Send Events Modes Available (291): 1, 0 libinput Send Events Mode Enabled (292):0, 0 libinput Send Events Mode Enabled Default (293):0, 0 Device Node (294): "/dev/input/event4" Device Product ID (295):9589, 49920 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773859] Re: upgrades to 18.04 fail
Can confirm that these steps BEFORE REBOOTING lead to a working 18.04 system after the 16.04 upgrade fails. Maybe these steps could be added to the upgrade script In psudocode: if [ error due to systemd1.service ] then; sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove exit fi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 853849] Re: Update Fails due to btrfs not being able to take a snapshot
Thanks, after loosing 4 terabytes of data due to buggy BTRFS, I moved away from the file system back to ext4. I still have the machine on a shelf for the day BTRFS becomes stable or gains recovery tools, so I can recover and access the data again. If you want to test this specific case then create a full disk BTRFS (no partition table) on a small disk SSD (128GB) and run the apt-btrfs- snapshot command with no arguments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/853849 Title: Update Fails due to btrfs not being able to take a snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/853849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281580] Re: [Intrepid] New Bluetooth Wizard fails to pair with devices: reintroduce hidd
Isn't bluetoothctl the current alternative to hidd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/281580 Title: [Intrepid] New Bluetooth Wizard fails to pair with devices: reintroduce hidd To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/281580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Done https://github.com/storaged-project/udisks/issues/723 ** Bug watch added: github.com/storaged-project/udisks/issues #723 https://github.com/storaged-project/udisks/issues/723 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
The Source code file location where this happens I'm pretty sure is
here:
/src/disks/gduwindow.c
/*
*/
static void
eject_cb (UDisksDrive *drive,
GAsyncResult *res,
gpointer user_data)
{
GduWindow *window = GDU_WINDOW (user_data);
GError *error;
error = NULL;
if (!udisks_drive_call_eject_finish (drive,
res,
))
{
gdu_utils_show_error (GTK_WINDOW (window),
_("Error ejecting media"),
error);
g_error_free (error);
}
g_object_unref (window);
}
static void
eject_ensure_unused_cb (GduWindow *window,
GAsyncResult *res,
gpointer user_data)
{
UDisksObject *object = UDISKS_OBJECT (user_data);
if (gdu_window_ensure_unused_finish (window, res, NULL))
{
UDisksDrive *drive = udisks_object_peek_drive (object);
udisks_drive_call_eject (drive,
g_variant_new ("a{sv}", NULL), /* options */
NULL, /* cancellable */
(GAsyncReadyCallback) eject_cb,
g_object_ref (window));
}
g_object_unref (object);
}
static void
on_devtab_drive_eject_button_clicked (GtkButton *button,
gpointer user_data)
{
GduWindow *window = GDU_WINDOW (user_data);
gdu_window_ensure_unused (window,
window->current_object,
(GAsyncReadyCallback) eject_ensure_unused_cb,
NULL, /* GCancellable */
g_object_ref (window->current_object));
}
/*
*/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858860
Title:
Gnome Disk Utility Issues incorrect command when ejecting a SATA
Harddisk or Solid State Drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858860] [NEW] Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Public bug reported: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "The Eject Button in Gnome Disk Utility" https://bugs.launchpad.net/bugs/1858860/+attachment/5318659/+files/2020-01-08%281%29EjectSATADriveButton.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Translation of the Error message to English: Removal of the medium has failed Error ejecting /dev/sdi: Command-line `eject"/dev/sdi"' exited with a non-zero status 1: eject: could not eject, last error: Incorrect ioctl() for device (udisks-error-quark, 0) So you can see in the error message that the incorrect command was used for the type of drive. ** Attachment added: "The Error in Dutch" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+attachment/5318663/+files/2020-01-08%282%29EjectSATAHDD_wrongCommand.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
So I took over the screen and see that there is a user prompt to upgrade. I chose the regular updates which included an update for the unattended upgrade package. I'll try to cancel and restart the Landscape process with the new unattended-upgrade package. ii unattended-upgrades1.10ubuntu5.2 all automatic installation of security upgrades ** Attachment added: "Not very unattended" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5308999/+files/2019-12-01NotVeryUnattendedUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Now 14 days into the upgrade. There has been no timeout of the process and it's still chugging along doing absolutely nothing at all. (see screenshot) ** Attachment added: "14 days in still no upgrade or timeout" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5308998/+files/2019-12-01Landscape14daysStuckUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Still running now 72 hours later with no progress. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] [NEW] LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Public bug reported: LANDSCAPE the licensed version is having troubles upgrading a Disco to Eoan machine. It's been running for 24 hours with no progress. Steps to reproduce * Click on Computers * Choose the computer to release upgrade * Click on Packages * Among the selected computers, 1 can be upgraded to a newer release. * Current Release * Upgrade Then wait, and wait and wait and wait some more. It's now been 24 hours and still no progress. Running htop doesn't show any obvious processes performing the upgrade and please see the screenshot as to the state of Landscape. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: landscape-client 18.01-0ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 21:57:40 2019 InstallationDate: Installed on 2019-02-22 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: landscape-client UpgradeStatus: Upgraded to disco on 2019-04-21 (211 days ago) ** Affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Here is the htop output of the machine 24 hours after clicking the upgrade button in Landscape. ** Attachment added: "HTOP output of the machine" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5306325/+files/2019-11-18htopUnattendedUpgrade24hours.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
root 1068 0.0 0.5 122408 22240 ?Ssl nov17 0:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal root 1125 0.2 0.7 47792 29684 ?Snov17 4:40 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/landscape-client.pid landsca+ 1126 0.1 1.5 435680 59080 ?Sl nov17 3:02 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint --quiet landsca+ 1128 0.2 1.2 147180 47872 ?Sl nov17 3:24 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint --quiet root 1135 0.1 1.0 57104 42276 ?Snov17 1:49 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint --quiet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
systemctl status landscape-client.service \u25cf landscape-client.service - LSB: Landscape client daemons Loaded: loaded (/etc/init.d/landscape-client; generated) Active: active (running) since Sun 2019-11-17 20:05:13 CET; 1 day 2h ago Docs: man:systemd-sysv-generator(8) Tasks: 8 (limit: 4487) Memory: 376.8M CGroup: /system.slice/landscape-client.service \u251c\u25001125 /usr/bin/python3 /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/landscape-client.pid \u251c\u25001126 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint --quiet \u251c\u25001128 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint --quiet \u2514\u25001135 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint --quiet nov 17 20:05:10 computer systemd[1]: Starting LSB: Landscape client daemons... nov 17 20:05:11 computer landscape-client[921]: * Starting the landscape-client daemon nov 17 20:05:13 computer landscape-client[921]:...done. nov 17 20:05:13 computer systemd[1]: Started LSB: Landscape client daemons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
systemctl status unattended-upgrades.service \u25cf unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-11-17 20:05:12 CET; 1 day 2h ago Docs: man:unattended-upgrade(8) Main PID: 1068 (unattended-upgr) Tasks: 2 (limit: 4487) Memory: 10.6M CGroup: /system.slice/unattended-upgrades.service \u2514\u25001068 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal nov 17 20:05:12 computer systemd[1]: Started Unattended Upgrades Shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Screenshot showing the lack of progress. Current time of the screenshot is 22:00 GMT+1 ** Attachment added: "24 hours no progress in the upgrade from Disco to Eoan" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5306324/+files/2019-11-18UpgradeDiscoToEon24HoursNoProgress.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I saved one 14.04.5 machine for this purpose. Will I be able to enabled -proposed for 14.04.5 even though it's now out of support? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825703] [NEW] Ubuntu 18.10->19.04 upgrade disables HDMI output and ssh during upgrade
Public bug reported: What Happened: When upgrading from 18.10 -> 19.04 about 10 minutes into the upgrade a dialog box shows up to remove old packages at this point the HDMI output and ssh servers are disabled so the only way to continue the upgrade is to physically go to the machine and plug in a VGA cable to an old monitor. What should have happened: Current Display output (In this case HDMI) and ssh access should be maintained during an upgrade of a system. Especially when there are user prompts. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco ubuntu-release-upgrader-gtk: Geïnstalleerd: 1:19.04.16.1 Kandidaat: 1:19.04.16.1 See here HDMI has been disconnected through software. The physical connection hadden't been touched. And even after unplugging and re- plugging the HDMI cable the result is the same. xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.02*+ 75.02 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) In settings only one display is shown. Turning the HDMI monitor off then on again with both VGA and HDMI connected restores the display. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 10:35:43 2019 InstallationDate: Installed on 2019-02-22 (57 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825703 Title: Ubuntu 18.10->19.04 upgrade disables HDMI output and ssh during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810997] [NEW] Indicator Printers Service opens too many dialog boxes when the paper is almost empty
Public bug reported: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service Printer is Epson TM-T88V Thermal Roll Receipt printer indicator-printers-service Description:Ubuntu 16.04.5 LTS Release:16.04 indicator-printers: Geïnstalleerd: 0.1.7+15.04.20150220-0ubuntu2 Kandidaat: 0.1.7+15.04.20150220-0ubuntu2 Versietabel: *** 0.1.7+15.04.20150220-0ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status What I Expected to Happen: One Dialog box, and if there is a reminder just refocus the already opened dialog box What really happens: 100's of dialog boxes are opened until the computer runs out of memory and becomes very slow Only way out is to killall indicator-printers-service See screenshot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-printers 0.1.7+15.04.20150220-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 8 21:37:25 2019 InstallationDate: Installed on 2016-11-26 (773 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: indicator-printers UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-printers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "screenshot of the phenomenon" https://bugs.launchpad.net/bugs/1810997/+attachment/5227746/+files/2019-01-08-PrinterProblemTooManyDialogs.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810997 Title: Indicator Printers Service opens too many dialog boxes when the paper is almost empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1810997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471723] Re: systemctl completion is slow
When is the fix going to be released? 18.04.1LTS takes still around 10
seconds to complete after
sudo systemctl start nameofser{TAB}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471723
Title:
systemctl completion is slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1471723/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773993] Re: Mouse cursor having a longer trail, lagging and stuttering
This is not fixed at all. Same issues still in kernel 4.15.0-39-generic see the attached screenshot ** Attachment added: "Screenshot proof of mouse lag and tearing on Ubuntu 18.04.1 LTS" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773993/+attachment/5218149/+files/mouseLagUbuntu18.04.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773993 Title: Mouse cursor having a longer trail, lagging and stuttering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
This issue is also happening in Ubuntu 16.04LTS with backports enabled. So I think there is something foobar with systemd-resolved and not resolvconf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cubic/+bug/1725840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
So physically at the machine it was only possible to log into the command prompt. There is no graphical interface available. To top it off Network manager was stopped! Not very good for network-manager to be stopped right after an upgrade. sudo service network-manager restart started the network, where I could resume fixing the computer over ssh. sudo apt install -f is my first course of action. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Ok so this is still FUBAR but then on a higher level. The upgrade failed miserably see the attached file. I was able to ssh into the machine after the upgrade. ran dpkg --reconfigure -a as suggested see below then I tried to reboot. which was a big mistake. when I try to reconnect to the remote machine ssh: connect to host remotemachine port 22: No route to host This is terrible. ssh should be like the first thing started always. even grub should have some kind of ssh feature so if the grub menu shows one could fix that remotely. Now I have a unusable machine and have to go physically to the location to try and reinstall everything by hand. == sudo shutdown --reboot 1 Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to start reboot.target: Failed to setup environment correctly See system logs and 'systemctl status reboot.target' for details. = It found too many errors to continue Errors found when configuring: libvlc5 libnss-winbind:amd64 ppp network-manager-pptp cups cups-daemon cups-core-drivers libpam-winbind:amd64 smbclient udev gnome-bluetooth libwayland-egl1-mesa:amd64 samba vlc-plugin-notify samba-common-bin bluez indicator-bluetooth network-manager-pptp-gnome hplip pulseaudio mountall unity-control-center printer-driver-hpcups libcogl20:amd64 initramfs-tools-core printer-driver-postscript-hp lvm2 libtotem0:amd64 libwebkit2gtk-4.0-37:amd64 libcheese-gtk25:amd64 libcanberra-pulse:amd64 libsolid4 initramfs-tools udisks2 upower xserver-xorg-input-vmmouse gnome-control-center libgtk-3-0:amd64 xserver-xorg-core gstreamer1.0-plugins-bad:amd64 winbind xserver-xorg-video-radeon libpeas-1.0-0:amd64 plymouth xserver-xorg libgstreamer-plugins-bad1.0-0:amd64 bamfdaemon xfce4-power-manager gnome-system-monitor network-manager kdelibs5-plugins Stopped configuring too many errors === ** Attachment added: "The upgrade file from Trust to Xenial from Landscape" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+attachment/5206437/+files/Upgrade_Trusty-Xenial.result.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
One quick little rant. Landscape is supposed to be Enterprise Grade software. I should be able to upgrade the releases of an entire farm of machines. This has been broken since the first time I tried this feature with Landscape. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at 10:00AM CEST so I'll let you know the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 777425] Re: Menus unusable with gnome3 when windows maximised
Still persists on Ubuntu 18.04. Gnome-shell will not let you right-click in a java application. Other desktop environments like Unity and Openbox(LXDE) don't have this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777425 Title: Menus unusable with gnome3 when windows maximised To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/777425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777238] Re: video lag
Another thing to note. The stutter (every 5 seconds a freeze frame) is consistently reproduce-able on Gnome on Ubuntu 18.04 but when you switch to Unity there is no stutter the video at all. So suspect that Gnome could also be playing a part in this issue. ** Summary changed: - video lag + video lag - Every 5 seconds a freeze frame when playing video of any source -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777238 Title: video lag - Every 5 seconds a freeze frame when playing video of any source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I have still have two machines that need upgrading from 14.04 -> 16.04 -> 18.04. I want to replace them and test the upgrade in the lab. The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788250] Re: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
The workaround to comment out the accessibility.properties does not work on Ubuntu 18.04.1 using the Unity desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788250 Title: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper To manage notifications about this bug go to: https://bugs.launchpad.net/jedit/+bug/1788250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788250] Re: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
Switching to the Official Oracle Java 8 Package was the workaround that worked for me. sudo add-apt-repository ppa:webupd8team/java sudo apt update sudo apt install oracle-java8-installer This bug caused downtime. Hopefully it will be given high priority to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788250 Title: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper To manage notifications about this bug go to: https://bugs.launchpad.net/jedit/+bug/1788250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787853] [NEW] SystemD's default TimeoutStart and TimeoutStop are too long for Desktop
Public bug reported: On Ubuntu 18.04LTS starting and stopping the computer is extremely slow. SystemD defaults to a start time timeout of 90seconds and a stop time timeout of 90seconds in the file /etc/systemd/system.conf This is great for huge databased raid systems in some cloud datacenter but is very inappropriate for desktop computing where there is a human waiting for the process. Ubuntu Desktops need to have the /etc/systemd/system.conf Set to timeout in less than <10 seconds (the magic computer irritation moment for humans) out of the box, default for example: DefaultTimeoutStartSec=9s DefaultTimeoutStopSec=9s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 23:12:49 2018 InstallationDate: Installed on 2015-11-15 (1008 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 08/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X99 Extreme11 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333 ** Affects: systemd (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/1787853 Title: SystemD's default TimeoutStart and TimeoutStop are too long for Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width
I can confirm that Martin Vysny's solution/workaround works in Ubuntu 18.04.1LTS. (this was not the case in Ubuntu Alpha when I reported this bug) Please note that you have to reboot (or log-off and logon again) for the system-monitor to show up in the gnome-tweaks extensions page. Time to say goodbye to indicator-multiload and thank Michael Hofmann for the years of enjoyment we had from his software indicator-multiload. Thank you Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714804 Title: Aardvark Daily: Indicator-Multiload doesn't show full-width To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Well gnome-shell crashed again and won't let me in again. whoopsie 35M aug 19 20:51 _opt_minergate_minergate.1000.crash I've attached a new previous boot ** Attachment added: "new previous boot" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+attachment/5177611/+files/previous_boot1.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Wrong crash file, oops (blush) I uploaded the gnome-shell one. whoopsie 114M aug 19 20:52 _usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787284] Re: Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity
*** This bug is a duplicate of bug 1188569 *** https://bugs.launchpad.net/bugs/1188569 @Khurshid Alam Unity is still supported as a community project. gnome-shell does not work in production for my business as it doesn't respond correctly to a touchscreen and I can't just stop my entire company and wait for months for a fix. The whole point is that we can choose whatever desktop environment that fits our needs. Unity migrated forward with 18.04 and should work exactly as it did in 16.04. The whole point of an upgrade is to improve the system. gnome-shell actually breaks Ubuntu to an unusable state. For businesses running in production this is not a reasonable expectation to just use gnome-shell. When a properly working desktop environment is available, namely Unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787284 Title: Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
So here is the upstream answer: Window decorations are client-side on wayland, that means they are just another part of the application window the same way as the products you are viewing. We cannot tell what parts of the window are decorations, or whether there are in fact any decorations at all. It's entirely up to applications to adjust to window state changes if they desire. (In the X11 session, there is a _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED hint that applications can set, and you'll find extensions that apply that to any windows. But X11 is a legacy technology at this point, and we won't add any features based on that.) As Ubuntu 18.04 is a LTS release still using X11 for compatibility can the Ubuntu project please add the _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED hint as a toggle? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
Upstream moved the bug to gtk-pixbuf as they knew of some problems with ico's in gdk-pixbuf https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/86 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787284] Re: Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity
*** This bug is a duplicate of bug 1188569 *** https://bugs.launchpad.net/bugs/1188569 The point of this bug is that it happens after an Upgrade. Something in the Upgrade process is breaking this behavior. Asking one to do a fresh install is not a reasonable solution. unity-settings-daemon -r ** (unity-settings-daemon:31635): WARNING **: 00:35:09.475: Name taken or bus went away - shutting down -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787284 Title: Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787285] Re: Extremely long boot times on Ubuntu 18.04.1
** Summary changed: - WindowsXP on a 386 boots faster than Ubuntu 18.04.1 + Extremely long boot times on Ubuntu 18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787285 Title: Extremely long boot times on Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1787285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
Reported upstream to the Gnome-shell devs https://gitlab.gnome.org/GNOME/gnome-shell/issues/493 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
BTW> Workaround to the buttons on the right (which only makes sense for right to left languages ) was to install Gnome-tweak tool. In Left to Right languages having the buttons on the left means less mouse travel on high res screens to click the button. This was just good well thought out and tested design. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
Here is the Upstream Bug report https://gitlab.gnome.org/GNOME/gtk/issues/1279 side note: When will Launchpad be updated with rich images and header templates like the gitlab bug tracker? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
I only have the default Ubuntu gnome-shell extensions installed as installing extensions from some gnome website still seems to me to be an extreme IT Security risk. I installed the gnome-tweak tool and lightdm the problem hasn't occurred anymore unless I try to log in with Wayland. Wayland gnome-shell login still crashes back to the greeter at every boot. Are you interested in the Wayland crashes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
The name of the crash file is _usr_bin_gnome-shell.1000.crash I uploaded it with ubuntu-bug How do I see the bug number it created? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Here is a copy of journalctl -b-1 > Previous_Boot.log ** Attachment added: "Previous Boot.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+attachment/5176514/+files/previous_boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results
Example of search query that Nautilus refuses to sort. ** Attachment added: "Example of where nautilus is not sorting" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+attachment/5176511/+files/Selectie_012.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698351 Title: Search in Nautilus Files does not allow sorting of results To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1698351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
Here is a PNG of the icon so you can see what it looks like if you are also on 18.04 with this bug. I used icotool -x pos.ico to extract the icons from the .ico file as PNGs ** Attachment added: "PNG version of the icon" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176039/+files/pos_5_48x48x8.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
And interestingly enough. Nautilus also displays the preview of the file as noise. ** Attachment added: "Nautilus also shows the icon as noise." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176038/+files/Schermafdruk%20van%202018-08-16%2000-36-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] [NEW] ".ico" icon files are shown as random noise
Public bug reported: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: gnome-shell (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/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
And here is the actual .ico file ** Attachment added: "the pos.ico file referred to by the desktop file" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176037/+files/pos.ico -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787294] Re: ".ico" icon files are shown as random noise
Here is a screenshot of the icon in gnome-hell ** Attachment added: "Corrupted Icon" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176036/+files/Schermafdruk%20van%202018-08-16%2000-33-47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787290] [NEW] Conky output is corrupted in gnome-shell Ubuntu 18.04.1
Public bug reported: Steps to reproduce upgrade from 16.04 to 18.04 Start your desktop with conky Conky output is corrupted. see screenshot. Log out of gnome-hell Log into Unity Conky output looks normal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: conky 1.10.8-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:15:45 2018 Dependencies: InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: conky UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: conky (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Here is what gnome-shell does to conky." https://bugs.launchpad.net/bugs/1787290/+attachment/5176027/+files/ConkyCorruption.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787290 Title: Conky output is corrupted in gnome-shell Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1787290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
See the screenshot 50px have been wasted here! On my 1280x1024 production screens for my business 50px is an extra line of text. Two if I use a smaller font. I noticed that the Opera browser has figured out a way around this and hides the unnecessary title bar when maximized. Maybe we can learn from Opera and make this behavior default? ** Attachment added: "50px wasted." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+attachment/5176024/+files/Schermafdruk%20van%202018-08-16%2000-07-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
See here in this screenshot. The 50px are used for the Application which is much more important than gnome-shell. ** Attachment added: "Opera browser gets rid of the title bar when maximized." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+attachment/5176025/+files/Schermafdruk%20van%202018-08-16%2000-11-52.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787288] [NEW] gnome-shell window title bar wastes space when maximized
Public bug reported: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: gnome-shell (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/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787285] [NEW] WindowsXP on a 386 boots faster than Ubuntu 18.04.1
Public bug reported: Steps to reproduce Upgrade from 16.04.5 to Ubuntu 18.04.1 Reboot the computer The computer takes several minutes to reboot The computer hangs on a purple screen not even showing the Ubuntu progress logo Eventually the login screen shows up. The hardware is 16-core processor 32gb RAM 2GB per second I/O m2.nvme SSD There is no excuse for these boot times. Ubuntu 12.04LTS booted in less than 10 seconds on the same hardware. What should happen. sudo reboot 10 seconds or less later greeter shows up login and use the computer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: plymouth 0.9.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Aug 15 23:15:02 2018 DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) dmi.bios.date: 08/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X99 Extreme11 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: plymouth (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/1787285 Title: WindowsXP on a 386 boots faster than Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1787285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787284] [NEW] Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity
Public bug reported: Steps to reproduce Upgrade a Ubuntu 16.04.5 machine to 18.04.1 Install LightDM (gdm3 doesn't allow me to log into my system) Install Unity (gnome3 won't start after one use) Try to open a terminal to do anything. CTRL+ALT+T Nothing happens. What should have happend A terminal should have opened. This is the Main most used keybinding for Ubuntu it should always be there, like CTRL+ALT+DEL on a windows machine! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity 7.5.0+18.04.20180413-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Aug 15 23:02:16 2018 DistUpgraded: 2018-08-15 21:57:03,781 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 18.03.00, 4.15.0-32-generic, x86_64: installed fwts-efi-runtime-dkms, 18.03.00, 4.4.0-131-generic, x86_64: installed nvidia, 390.48, 4.15.0-32-generic, x86_64: installed nvidia, 390.48, 4.4.0-131-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:1151] InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 SourcePackage: unity UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) dmi.bios.date: 08/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X99 Extreme11 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 15 22:48:13 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787284 Title: Upgrade to Ubuntu 18.04.1 from 16.04.5 breaks terminal keybindings in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787282] [NEW] Ubuntu 18.04.1 Nautilus can't sort search results by Name, Size, Type or Location by clicking on the column title
Public bug reported: Steps to reproduce Switch to LightDM Switch to Unity (gnome wouldn't let me log in so I was looking for the log file) Open Nautilus in the search bar type ".log" (without the quotes) All the log files in your home directory are shown Click on Name column nothing happens click on the Size column nothing happens Click on a folder in nautilus containing items Click on the Name column The column gets sorted by name Click on the size column the column gets sorted by size The behavior should be the same whether or not you have searched but it's not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Aug 15 22:52:39 2018 InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot of the area not sorting" https://bugs.launchpad.net/bugs/1787282/+attachment/5175959/+files/Selectie_012.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787282 Title: Ubuntu 18.04.1 Nautilus can't sort search results by Name, Size, Type or Location by clicking on the column title To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778421] [NEW] Ubuntu 18.04 vino does not start up at boottime unable to login with gdm over vino
Public bug reported: == Release == Description:Ubuntu 18.04 LTS Release:18.04 Ubuntu Gnome desktop gdm login manager == Package version == vino: Geïnstalleerd: 3.22.0-3ubuntu1 Kandidaat: 3.22.0-3ubuntu1 Versietabel: *** 3.22.0-3ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status == Expected occurrence == set up two users on the system Install vino Enable remote desktop sharing for both users Set a password (8 char wtf) reboot Open Remmina on another computer Set up the connection vnc over ssh double click the connection Remmina VNC shows the gdm login screen and allows me to choose a user Enter that users desktop do some work Choose Switch User Switch to the other user and use that desktop logoff the users show the gdm screen == What really happens == >From step double click the connection Remmina show a black screen, no gdm ss -lnt shows no services listening on port 5900 physically login behind the machine that is going to be placed remotely restart remmina am able to log in to the logged in desktop switch users vino sends a black screen from gdm log in physically to the 'remote' machine vino still sends a black screen reboot the computer more black screen in 16.04 I used X11vnc together with a systemctrl x11vnc.service file which worked fine. This is also broken in 18.04. Tried a vino.service file from one of the forums didn't work vino fails with vino.service - description about the service Loaded: loaded (/lib/systemd/system/vino.service; enabled; vendor preset: ena Active: failed (Result: exit-code) since Sun 2018-06-24 20:18:23 CEST; 26min Process: 1147 ExecStart=/usr/lib/vino/vino-server (code=exited, status=1/FAILU Main PID: 1147 (code=exited, status=1/FAILURE) jun 24 20:18:23 computer systemd[1]: Started description about the service jun 24 20:18:23 computer vino-server[1147]: Unable to init server: Kon nie jun 24 20:18:23 computer vino-server[1147]: Kan scherm ‘’ niet openen jun 24 20:18:23 computer vino-server[1147]: Voer ‘vino-server --help’ uit jun 24 20:18:23 computer systemd[1]: vino.service: Main process exited, co jun 24 20:18:23 computer systemd[1]: vino.service: Failed with result 'exi lines 1-12/12 (END) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 24 20:23:08 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (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/1778421 Title: Ubuntu 18.04 vino does not start up at boottime unable to login with gdm over vino To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1778421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736576] Re: apt related unit test errors in artful, bionic
This is still broken in Bionic with landscape-client The proposed patch does not work. landscape-client: Geïnstalleerd: 18.01-0ubuntu3.1 Kandidaat: 18.01-0ubuntu3.1 Versietabel: *** 18.01-0ubuntu3.1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.01-0ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Traceback (most recent call last): File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 653, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 95, in result.addCallback(lambda x: self.detect_changes()) File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 543, in detect_changes deferred = self.detect_packages_changes() File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 551, in detect_packages_changes if self._got_task or self._package_state_has_changed(): File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 577, in _package_state_has_changed last_changed = os.stat(f).st_mtime FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/lists/_var_lib_landscape_client_package_binaries_._Packages' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736576 Title: apt related unit test errors in artful, bionic To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1736576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778395] [NEW] Landscape: unable to apply package profile _var_lib_landscape_client_package_binaries_._Packages Not Found
Public bug reported: == release == Description:Ubuntu 18.04 LTS Release:18.04 == package == landscape-client: Geïnstalleerd: 18.01-0ubuntu3.1 Kandidaat: 18.01-0ubuntu3.1 Versietabel: *** 18.01-0ubuntu3.1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.01-0ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages == What was expected == In landscape I have a package profile that installs the packages I need for a fresh prep of a new machine. I expected to add the machine to the tagged profile and have all the packages install on the machine so I could come back an hour later and finish prepping the machine for production. == What happened instead == Landscape reported Failed The following packages have unmet dependencies: landscape-profile-globeone5-kassabasisinstall: Depends: byobu but is not installable landscape-profile-globeone5-kassabasisinstall: Depends: curl but is not installable landscape-profile-globeone5-kassabasisinstall: Depends: dkms but is not installable landscape-profile-globeone5-kassabasisinstall: Depends: fail2ban but is not installable Yet when I install the packages manually with 'sudo apt install packagename' then the packages install normally. In /var/log/landscape/package-reporter.log the following error is shown around the same time the package profile was being installed (see attachment for the entire log file) 2018-06-24 12:17:05,267 INFO [MainThread] Queuing message with changes in known packages: 1 installed, 0 available, 0 available upgrades, 0 locked, 0 autoremovable, 0 not installed, 0 not available, 0 not available upgrades, 0 not locked, 0 not autoremovable. 2018-06-24 12:18:58,557 ERROR[MainThread] None Traceback (most recent call last): File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 653, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 95, in result.addCallback(lambda x: self.detect_changes()) File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 543, in detect_changes deferred = self.detect_packages_changes() File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 551, in detect_packages_changes if self._got_task or self._package_state_has_changed(): File "/usr/lib/python3/dist-packages/landscape/client/package/reporter.py", line 577, in _package_state_has_changed last_changed = os.stat(f).st_mtime FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/lists/_var_lib_landscape_client_package_binaries_._Packages' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 24 12:24:14 2018 InstallationDate: Installed on 2018-06-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "The full contents of the package-reporter.log showing the error" https://bugs.launchpad.net/bugs/1778395/+attachment/5156087/+files/package-reporter.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778395 Title: Landscape: unable to apply package profile _var_lib_landscape_client_package_binaries_._Packages Not Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1778395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776059] Re: landscape-broker segfaults killing network connection and touchscreen driver
Jun 9 18:36:29 machine sshd[10309]: Failed password for root from $EVILIP port 60394 ssh2 Jun 9 18:38:25 machine sshd[10335]: Server listening on 0.0.0.0 port 22. Jun 9 18:38:25 machine sshd[10335]: Server listening on :: port 22. Jun 9 18:38:39 machine sshd[10339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=$EVILIP user=root Jun 9 18:38:25 tilburg-kassa kernel: [41888.700394] BUG: unable to handle kernel paging request at ff60 I notice on the same timestamp that ssh does a Server listening on 0.0.0.0 port 22 But for the SSHD error nothing in the log. Jun 9 19:05:33 tilburg-kassa kernel: [43516.157000] traps: sshd[10982] trap invalid opcode ip:7ff469ac8d40 sp:7fffb13fe488 error:0 in pam_unix.so[7ff469ac1000+e000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776059 Title: landscape-broker segfaults killing network connection and touchscreen driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776059] Re: landscape-broker segfaults killing network connection and touchscreen driver
Here is Swap usage over 3 days. ** Attachment added: "Swap usage over 3 days" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+attachment/5151421/+files/Swap_3-day.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776059 Title: landscape-broker segfaults killing network connection and touchscreen driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776059] Re: landscape-broker segfaults killing network connection and touchscreen driver
Heres a 3-day graph from landscape showing that memory never reaches more that 57 used. The gap of course being the downtime caused by this bug. ~$ free -h totalusedfree shared buff/cache available Mem: 3,8G959M2,0G 28M819M2,6G Swap: 3,9G 0B3,9G FilenameTypeSizeUsedPriority /dev/dm-1 partition 4112380 0 -1 ** Attachment added: "3-day graph of memory including outage" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+attachment/5151420/+files/Memory3-day.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776059 Title: landscape-broker segfaults killing network connection and touchscreen driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776059] Re: landscape-broker segfaults killing network connection and touchscreen driver
Here are the requested log files including the Landscape error ** Attachment added: "kern.log and kern.log.1" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+attachment/5151369/+files/KernelLogs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776059 Title: landscape-broker segfaults killing network connection and touchscreen driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776059] [NEW] landscape-broker segfaults killing network connection and touchscreen driver
Public bug reported: Every week on Sunday morning one of my Ubuntu 16.04 machines goes into a non-usable state. The log file shows the last entry in the log is landscape-broke[1164]: segfault at 0 ip 0049469d sp 7ffe06803db0 error 4 in python2.7[40+2de000] All logging stops the screen only shows the background and the only way out is to 5 second press the power button on the computer which then restores the computer to a usable state again. Sunday mornings the computer is idle, and sleep state has been turned off ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: landscape-client 16.03-0ubuntu2.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 10 11:35:46 2018 InstallationDate: Installed on 2015-04-29 (1137 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: Upgraded to xenial on 2017-03-05 (461 days ago) ** Affects: landscape-client (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/1776059 Title: landscape-broker segfaults killing network connection and touchscreen driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1776059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
Didn't help after all. Plymouth is still using 100% CPU on reboot. Now trying all the suggestions in https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771 Disabled plymouth in Grub and dpkg-reconfigured it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
I found the conflict with the eGalax Touch Daemon driver. I moved the driver startup from /etc/init.d/eGtouch.sh to userspace as I don't need the touchscreen at login. The strange thing is I have 17 machines with this configuration and only one is exhibiting this behaviour with plymouthd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
I've attached an apport report of the runaway process ** Attachment added: "apport.plymouth.b8ut5mm8.apport" https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
There is a regression of this bug in 16.04.4LTS Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 388 root 20 0 201472 100776 8516 R 95,7 2,9 19:57.46 plymouthd ii liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 amd64LightDM GObject client library ii lightdm 1.18.3-0ubuntu1.1 amd64Display Manager -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759494] [NEW] system-config-lvm package missing from 18.04LTS Bionic Beaver
Public bug reported: Package "system-config-lvm" is not compatible with Wayland so was in some strange logic removed from the repositories in 17.10. This, even though we could switch back to Xorg, which we did anyway since Wayland is far from production ready. Luckily with 18.04LTS Xorg will be default, meaning we can use system- config-lvm again. Please re-add it to the Ubuntu Repositories for 18.04LTS and include it in the LiveISO (USB, CD). It's really the only GUI utility to configure LVM's properly. Since Ubuntu's default LVM creation in Ubiquity does not allow you to specify a volume group name and separate the root from home logical partitions. Using a GUI to configure LVM is much better than using the command line as one can better visualize the results of ones actions. Thanks! ** Affects: system-config-lvm (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/1759494 Title: system-config-lvm package missing from 18.04LTS Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-lvm/+bug/1759494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759482] Re: cgmanager saturates one core reproduction Bug #1302436
I created a stack trace on the runaway process. Hopefully this helps to find the problem (see attachment) ** Attachment added: "Stacktrace of runaway cgmanager process" https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1759482/+attachment/5093152/+files/cgmanager.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759482 Title: cgmanager saturates one core reproduction Bug #1302436 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1759482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759482] [NEW] cgmanager saturates one core reproduction Bug #1302436
Public bug reported: was able to reproduce this error. There is a rotating background every 60 seconds and a java application open. Don't know if these are the cause of the cpu being eaten up by this process. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 316 root 20 0 23672 2480 2348 S 62,6 0,1 321:39.34 cgmanager Release:14.04 Codename: trusty cgmanager: Geïnstalleerd: 0.24-0ubuntu7.5 Kandidaat: 0.24-0ubuntu7.5 Versietabel: 0.39-2ubuntu2~ubuntu14.04.1 0 100 http://nl.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 0.24-0ubuntu7.5 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.24-0ubuntu7.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 0.24-0ubuntu5 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Package ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cgmanager 0.24-0ubuntu7.5 ProcVersionSignature: Ubuntu 4.4.0-117.141~14.04.1-generic 4.4.114 Uname: Linux 4.4.0-117-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 28 08:22:13 2018 InstallationDate: Installed on 2015-11-27 (851 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: cgmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759482 Title: cgmanager saturates one core reproduction Bug #1302436 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1759482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302436] Re: cgmanager saturates one core
** Changed in: cgmanager (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302436 Title: cgmanager saturates one core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1302436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
