[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

2022-12-07 Thread Benjamin Schmid
Even as a decade-old Ubuntu user this "The following packages have been kept back:" was a UX nightmare for me. It took me several runs of article reading, many unsuccessful "apt-mark showhold", breaking "apt install X" runs and still no clue at all about the background on these errors suddenly

[Touch-packages] [Bug 1783795] Re: After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …

2018-07-26 Thread Benjamin Schmid
** Attachment added: "Corrupted update-mamager screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783795/+attachment/5168198/+files/corrupted-update-manager.png ** Attachment removed: "DpkgLog.txt"

[Touch-packages] [Bug 1783795] [NEW] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …

2018-07-26 Thread Benjamin Schmid
Public bug reported: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the

[Touch-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby

2016-11-06 Thread Benjamin Schmid
** Tags added: regression-update yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1618839 Title: Regression: WiFi connection reconnects, but dead, after

[Touch-packages] [Bug 1618839] Re: Regression: WiFi connection reconnects, but dead, after waking from standby

2016-11-06 Thread Benjamin Schmid
Same issue here after upgrading from xenial 16.04 to yakkety 16.10: After standby I can ping valid IP addresses, but DNS fails. Restarting the network manager via ` sudo /etc/init.d/network-manager restart` does mend the situation. In this SO post https://askubuntu.com/q/837575/94728 people