[Bug 1884810] Re: Anbox doesn't start, /dev/binder isn't created (20.04)
/dev/binder is obsolete. Installing the binder_linux module creates a filesystem type now. https://brauner.github.io/2019/01/09/android-binderfs.html Summary (excerpts, see the blog entry link for more): Problem 1: Using the misc major Device Number Problem 2: Containers and IPC namespaces To solve both problems we came up with a solution that I presented at the Linux Plumbers Conference in Vancouver this year. Android binderfs is a tiny filesystem that allows users to dynamically allocate binder devices, i.e. it allows to add and remove binder devices at runtime. mkdir /dev/binderfs mount -t binder binder /dev/binderfs See also https://askubuntu.com/questions/1267990/ls-1-dev-ashmem-binder-yields-anticipated-result-for-dev-ashmem-but-an-err -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884810 Title: Anbox doesn't start, /dev/binder isn't created (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1884810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922468] [NEW] package node-ci-info (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: Updater found older version of node-ci-info package. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: node-ci-info (not installed) ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 4 02:09:27 2021 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-30 (5 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: node-ci-info Title: package node-ci-info (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: node-ci-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922468 Title: package node-ci-info (not installed) failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-ci-info/+bug/1922468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Can't switch to HSP profile with my Aftershokz. Says: "Failed to change profile to headset_head_unit" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910496] Re: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
For future reference, if anyone has the same issue I fixed it by upgrading the driver to the version `nvidia-driver-460`. So fix: ``` # Allow yourself to get the newest driver versions sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt install nvidia-driver-460 ``` I also threw in a `sudo apt-get purge nvidia*` for good measure. I did have to `cd /` otherwise the purge would fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910496 Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1910496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910496] Re: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
I've also faced this issue, and after trying out some of the older drivers I can also confirm that nvidia-graphics-435 also doesn't work. This is my first post on the forum, and as such if I need to reformat it or create a new ticket I'd thank you for telling me so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910496 Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1910496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818680] Re: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front
** Summary changed: - Title + [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818680 Title: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/818680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820092] Re: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all
** Summary changed: - Title + [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820092 Title: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/820092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943674] Re: Upstream release 2.7.0 of purple plugin pack
** Summary changed: - Title + Upstream release 2.7.0 of purple plugin pack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943674 Title: Upstream release 2.7.0 of purple plugin pack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/purple-plugin-pack/+bug/943674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 256670] Re: When you click a JAR the current directoy should be that of the JAR, not your home
** Summary changed: - Title + When you click a JAR the current directoy should be that of the JAR, not your home -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/256670 Title: When you click a JAR the current directoy should be that of the JAR, not your home To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/256670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 818680] Re: Title
** Summary changed: - [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front + Title -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818680 Title: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/818680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 256670] Re: Title
** Summary changed: - When you click a JAR the current directoy should be that of the JAR, not your home + Title -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/256670 Title: When you click a JAR the current directoy should be that of the JAR, not your home To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/256670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820092] Re: Title
** Summary changed: - [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all + Title -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820092 Title: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/820092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943674] Re: Title
** Summary changed: - Upstream release 2.7.0 of purple plugin pack + Title -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943674 Title: Upstream release 2.7.0 of purple plugin pack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/purple-plugin-pack/+bug/943674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883615] [NEW] package python3-aiozmq 0.7.1-2 failed to install/upgrade: installed python3-aiozmq package post-installation script subprocess returned error exit status 1
Public bug reported: apt-get install python3-aiozmq ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-aiozmq 0.7.1-2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 15 16:36:47 2020 ErrorMessage: installed python3-aiozmq package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-30 (77 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: aiozmq Title: package python3-aiozmq 0.7.1-2 failed to install/upgrade: installed python3-aiozmq package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aiozmq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883615 Title: package python3-aiozmq 0.7.1-2 failed to install/upgrade: installed python3-aiozmq package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiozmq/+bug/1883615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275561] Re: gpaint has no undo funtionality
And 10 years later still no undo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/275561 Title: gpaint has no undo funtionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpaint/+bug/275561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I attached the Realtek dump with my headphones plugged into the jack for comparison. ** Attachment added: "RtHDDump.txt.headphonesInJack" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353097/+files/RtHDDump.txt.headphonesInJack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Exactly the same problem with Samsung Notebook 9 Pro (np930mbe-k04us) which also has an ALC298. Headphones are working with model=mono-speakers. I attached my Realtek dump. I'm also soliciting the arch forum for help (I'm running arch): https://bbs.archlinux.org/viewtopic.php?pid=1897858 ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353056/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861615] [NEW] package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: didnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Feb 2 08:12:58 2020 DuplicateSignature: package:libldap-2.4-2:amd64:2.4.45+dfsg-1ubuntu1.4 Setting up libkf5notifications-data (5.44.0-0ubuntu1) ... dpkg: error processing package libldap-2.4-2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-02-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: openldap Title: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861615 Title: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1861615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
Same problem on Ubuntu 19.10 on HP 250 G7. Tried editing logind.conf as per previous suggestions, but no combination solved the problem. Tried installing pm-utils, which weren't installed (see #117), that didn't help either. Tried turning off the automatic suspend and automatic blank screen in the Power settings, thinking that they might for whatever reason be interfering; no success. Tried uncommenting InhibitDelayMaxSec, HoldoffTimeoutSec and LidSwitchIgnoreInhibited (with both 'yes' and 'no'), none of those did it. Closing the lid only blanks the screen (fans are running), even if I leave it for some time. Opening the lid turns the screen back on, but doesn't open up the login screen. Besides the unsuccessful editing of logind.conf, the only other concurrent issue that I haven't found anyone else encountering, is that, in my case, closing the lid and then opening it also turns on Airplane mode, and then the next time I close it and open it, it turns the Airplane mode off. As I often need a quick suspend, as a temporary workaround, I set it up so that the physical power button suspends it. This works as intended, without any problems, so instead of having to close the lid, I have to press the button, then close the lid. It's better than having to open the top right menu, press Alt and click suspend, then close the lid, every time, but I'd still like to solve the problem properly... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850016] [NEW] undocumented mouse button 9 response
Public bug reported: There is an undocumented mouse button 9 response that is redundant with the documented mouse binds & serves no purpose. But it does interfere with my desire to use button 9 for my own purposes. I sure would like to know how to fix this. ** Affects: viewnior (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/1850016 Title: undocumented mouse button 9 response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/viewnior/+bug/1850016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820385] [NEW] Ubuntu 18.04 to 18.10 This upgrade software shows "could not calculate the ugprade"
Public bug reported: I am attempting to upgrade from ubuntu 18.04 to 18.10 using this upgrade software, as soon as it gets to part where it says "calculating changes" i get that error "could not calculate the ugprade", i could not find anything about it. on those versions ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.30 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Sat Mar 16 10:57:06 2019 InstallationDate: Installed on 2019-02-22 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-03-16 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2019-03-08T20:17:21.674317 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1820385 Title: Ubuntu 18.04 to 18.10 This upgrade software shows "could not calculate the ugprade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1820385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I have a USB-connected brother printer/scanner MFC-7420, hooked up to a
desktop running xubuntu 18.04.1 The printer works but the scanner does
not. I have tried pretty much every heck posted here and elsewhere but
to no avail. Here's what I have done and the error messages I got.
Heads up: I wonder what's the significance on the discrepency in (3)
below?
-
0) To install the drivers I following the instruction (+FAQ) on
https://support.brother.com/g/b/downloa ... all=128
including brother-udev-rule-type1-1.0.2-0.all.deb. The printer works, but not
the scanner.
-
1) Xsane says
Failed to open device `brother2:bus2;dev5'
Invalid argument.
(sudo xsane gives the same error message). When I fire up simple-scan
(sudo or otherwise) it says
Ready to Scan
Brother MFC-7420
but when I click "scan" I got "Unable to connect to scanner".
-
2) scanimage -L
device `brother2:bus2;dev5' is a Brother MFC-7420 USB scanner
scanimage --test
scanimage: open of device brother2:bus2;dev5 failed: Invalid argument
-
3) lsusb
Bus 001 Device 002: ID 04f9:0180 Brother Industries, Ltd MFC-7420
[ Question: How come it says 001:002 when xsane complains about 002:005
?!! ]
ls -l /dev/bus/usb/001/002
crw-rw-r--+ 1 root lp 189, 1 Jan 17 15:36 /dev/bus/usb/001/002
ls -l /dev/bus/usb/001
total 0
crw-rw-r-- 1 root root 189, 0 Jan 17 15:27 001
crw-rw-r--+ 1 root lp 189, 1 Jan 17 15:36 002
crw-rw-r-- 1 root root 189, 2 Jan 17 15:27 003
crw-rw-r-- 1 root root 189, 3 Jan 17 15:27 004
crw-rw-r-- 1 root root 189, 4 Jan 17 15:27 005
crw-rw-r-- 1 root root 189, 5 Jan 17 15:27 006
[Question: According to
https://cromwell-intl.com/open-source/x ... ument.html
the command above should have listed "scanner" but as you can see it's not
there]
---
4) I have copied files from lib64 to lib, such as
sudo ln -sf /usr/lib64/libbrscandec*.so* /usr/lib
Reboot but to no avail.
---
5) I added myself to the scanner group:
sudo usermod -a -G scanner (me)
Reboot but to no avail. I also tried
more /etc/group | grep -n scanner
and here's the output:
59:scanner:x:120:saned,(me)
6) I edited /lib/udev/rules.d/60-libsane1.rules following the heck in (#12 of)
https://easylinuxtipsproject.blogspot.c ... nters.html
Reboot but to no avail.
7) There is no "brother.conf" in /etc/sane.d
8) I used synaptic to delete all "brother" related files, reinstall the drivers
in (step 0) above, reboot but to no avail.
9) I added the following two lines at the end of
/lib/udev/rules.d/40-libsane.rules (Before the line "# The following rule will
disable ...")
# Brother scanners
ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"
Reboot but to no avail.
I'm at a lost on what to do. The scanner (again, it's USB-based, not wireless)
worked until window, but I no longer have access to the window machine and I
really need the scanner for work. Your help and advice is most welcome. THANKS!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728012
Title:
Many 3rd party scanner drivers are broken by a sane change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810009] [NEW] cannot install texlive fonts in 18.04
Public bug reported: I installed from scratch lubuntu 18.04.1 on my 32-bit netbook (previously running lubuntu 16.04). The installation went well and I was able to reboot the machines and installed other (non-tex-related) softwares. But when I tried to install texlive-latex I got massive errors. Eventually I tracked down the problem to a single package, fonts-lmodern. I used synaptic to purge all texlive related packages and then installed fonts-lmodern to isolate this one error message: W: Failed to fetch http://ftp.utexas.edu/ubuntu/pool/main/l/lmodern/fonts-lmodern_2.004.5-3_all.deb Connection failed [IP: 146.6.15.16 80] I posted this question in the "answers" sections of launchpad and eventually got help resolving this problem: https://answers.launchpad.net/ubuntu/+source/texlive- extra/+question/677188 Solution: edit /etc/apt/source.list by replacing all the http by https Note: (1) I ran into this problem with multiple texlive fonts; fonts- lmodern just happened to be the first one synaptic complained about. (2) These fonts packages (over 40 of them) are installed as part of texlive-latex-base; until I edited source.list as described above I was not able to install latex. Presumably that is an important tool for many people (certainly for me) so I report the bug (?) here, even though the answer section already resolves the issue. (3) I ran into this same issue in linux mint 19.1 xfce on a 64bit laptop. Mint's has a different repo setup and I have not yet figured out how to fix this. I also know that launchpad is not responsible for mint. I mention this solely to point out that (I believe) this is not a "32 bit issue". THANKS! ** Affects: texlive-extra (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/1810009 Title: cannot install texlive fonts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1810009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
The issue now appears resolved with hwe-18.04/4.18.0-13, /sys/bus/iio is now present and the functionality has been restored. Summary: /sys/bus/iio appears to be missing on all the bionic 4.15.* kernel releases (including 4.15.0-43) but is present on xenial 4.4 and cosmic 4.18 (at least as of 4.18.0-13). Here is to hoping there is not a similar kerfuffle with RNGs and stuff :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
https://news.ycombinator.com/item?id=18711970 The sad state of being able to use Ubuntu on touch devices (hint: you can't) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807250 So, apparently support for an entire bus class has been missing since ubuntu bionic (18.04 LTS) was released in april. Using kernels from other distros or ubuntus old xenial 4.4.0-134 all provide access to sensor data, suggesting the issue is with current (and shipped) kernels. Three weeks into this not much is happening even though the issue also affect canonical-specific 4,18 kernels. This all suggests that pretty much no one has been using ubuntu on touch devices otherwise i wouldn't be the first one to notice this. Now that the devs know this they have no time for it... ** Also affects: gdm3 (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/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy
is /dev/bus/iio even properly populated? See LP: #1807250 LP: #1804804 LP: #1792813 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778476 Title: [bionic] high cpu load HP probook iio-sensor-proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804804] Re: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)
Confirmed in LP: #1807250 and LP: #1792813̈́ Ubuntu kernels >=4.15 are the culprit, does not affect debian 4.18.20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804804 Title: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792813] Re: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10
LP: #1807250 Xenials kernel 4.4.0-134, debian stable kernel 4.9.8, debian testing kernel 4.18.20 are all working when booted with bionic userspace. According to nacc upcoming cosmic 4.18 is also affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792813 Title: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system
Yeah, so this is like the person who started complaining about this stuff which was totally confirmed by nacc. Exceedingly fun fact: current bionic userspace/install booted with debian stable kernel 4.9, debian testing kernel 4.18 and ye olde xenial 4.4.0-134 is working just fine *indicating* that support for an entire bus class has been missing/faulty in ubuntu >=4.15 since bionic launch like way back before everyone knew the name Cambridge Analytica and that girl with the weird teeth from "Smallville" was charged with human trafficking or whatever. I realize that people have selfies to take and like totally have to spend a lot of time placating their friends about their issues and stuff but that no one noticed this until now is kinda disturbing and I like totally have to resist the urge to somehow implicate Kylie Jenner in this. The reason for the attitude is that i had to complete a friggin js- required Scroogle puzzle to state the obvious. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807250 Title: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
everlasting bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
möp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730143] Re: no response to scroll wheel
TBH, I don't understand you. As indicated my Ncurses version is 6 something. I don't have a clue how it was compiled since I installed it with apt-get from the standard Ubuntu repo. Are you saying I should try compiling it myself? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730143 Title: no response to scroll wheel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/1730143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747226] [NEW] Installation crashes during "Creating user..."
Public bug reported: I have experienced this bug many many times. The laptop I am using is a Lenovo ThinkPad P71. I have removed the SSD from my laptop, shut down, connected an external hard drive, and booted from a USB with Ubuntu 16.04. The installer obviously recognizes the external hard drive as the main storage device. I do this because I want Ubuntu with full disk encryption installed on an external hard drive. When I get to the screen that asks for a username and password for the computer, I input the information. Then I proceed and it loads for about 10 minutes before doing anything. Then the installer proceeds for a while, and in the bottom left it shows what the installer is working on. When it gets to "Creating user..." it crashes 99% of the time. After attempting to install over 10-15 times, it occasionally does NOT crash, and installs correctly at this step. I have no idea why... This bug DOES NOT happen if I do not select encrypt the disk. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Sat Feb 3 22:20:50 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747226 Title: Installation crashes during "Creating user..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1747226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Hi Pat (paett) you write in #122 "So here i am sitting scrolling Down with my Touchpad (Scroll Gesture not working) but Toupad is." So does it work or not? Legacy (simple pointing device) is working since long time. But it's not usable like this. The question is how you a scrolling on the touchpad without gestures? "After that i installed a complete new Version of Ubuntu 17.10 with full whip of Ubuntu 16.04-r3, since i wanted to install the Git Solution on 17.10 And to my Surprise the mouse was working out of the Box (SecureBoot still disabled)." Again, what is working? Simple pointing device or touch gestures (e.g. two finger scrolling etc.)? Thank's for your efforts and hopefully ELAN Microelectronics Corp. is getting things done (even tough I doubt because this device is years old and probably not manufactured anymore!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867507] Re: [needs-packaging] pypy
Is there any chance you can add a PyPy3 version to this PPA? Right now, there's no nice way to get system-wide installs of PyPy3 on Ubuntu that I can find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867507 Title: [needs-packaging] pypy To manage notifications about this bug go to: https://bugs.launchpad.net/pypy/+bug/867507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
As my Lenovo B50-30 is also affected, you can add IdeaPad 305-15IBY, Lenovo B40-30, B50-30, B50-30 Touch, E40-30 BIOS Ver. 9CCN35WW20 15/11/18 to the list (all have the same BIOS). Thanks to canonical for bricking my laptop... another disservice to GNU/Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739435] [NEW] tried to install WattOS 32bit on a VM in VirtualBox5.1.30118398 (Qt5.6.3) r. Installation crashed
Public bug reported: VirtualBox is running on a MacBook Pro (early 2011) i7 (2nd gen.) 8GB RAM; 256GB SSD ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 [modified: usr/share/ubiquity/apt-setup] ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CasperVersion: 1.376 Date: Wed Dec 20 15:47:15 2017 LiveMediaBuild: wattOS-R10-32bit 16.04 - Release i386 ProcEnviron: LANGUAGE=de_DE.UTF-8 TERM=unknown PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UbiquitySyslog: UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug custom i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739435 Title: tried to install WattOS 32bit on a VM in VirtualBox5.1.30118398 (Qt5.6.3) r. Installation crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1739435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized
*** This bug is a duplicate of bug 1400463 *** https://bugs.launchpad.net/bugs/1400463 I think the kernel-bug-exists-upstream See here: https://marc.info/?l=linux-input=150150074208646 ** This bug has been marked a duplicate of bug 1400463 [Medion Akoya P2214T] Touchpad not properly recognized -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738839 Title: [Medion S2217] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738839 Title: [Medion S2217] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738839] [NEW] [Medion S2217] Touchpad not properly recognized
Public bug reported: The ELAN (not Elantech) touchpad in my Medion S2217 laptop is not properly recognized. The touchpad shows up as an ITE Tech. Inc. ITE Device(8910) and works only as a plain pointing device. Multitouch and scrolling or anything else however, do not function, nor do options for this show up in the Mouse & Touchpad options in Ubuntu. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: input legacy s2217 touch touchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738839 Title: [Medion S2217] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738839] Re: [Medion S2217] Touchpad not properly recognized
Tested with: - ubuntu 16.04 - ubuntu 16.10 - ubuntu 17.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738839 Title: [Medion S2217] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Reply from Vendor: --- Dear Input Maintainer, Nice to get your email. ITE is chip provider. I am sorry that I do not have info related customer’s design. You might contact with notebook vendor to get support. Thanks. Mitch 從: ITE Tech. Inc. [no-re...@ite.com.tw] 寄件日期: 2017年12月13日 下午 02:59 至: Input Maintainer 主旨: ITE 聯陽半導體-聯絡我們通知信 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
What a sh*t. Thank's Mizuti and every contributor for hunting an following this bug. Sometimes it's not enough... anyway it's really sad that the responsible input maintainers are not even willing to respond... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Somebody can tell where to follow the input maintainers? Thank's! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730143] [NEW] no response to scroll wheel
Public bug reported: ". . . new in htop 2.0 . . . If you're using NCurses 6, htop will also support your mouse wheel for scrolling." -- https://hisham.hm/htop/ Doesn't work for me. No response to scroll wheel. Any suggestions? I'd really like to make this work. htop 2.0.1 ncurses-bin 6.0+20160213-1ubuntu1 Ubuntu 16.04 LTS Xenial, 64 bit kernel 4.4.0-98-generic xorg 1:7.7+13ubuntu3 openbox 3.6.1-1ubuntu2 and that's it. No further DE beyond openbox. System was built from the mini.iso. Tried in all the following terminals: lxterminal 0.2.0-1ubuntu0.1 xterm 322-1ubuntu1 terminator 0.98 xvt 2.1-20.1ubuntu1 ** Affects: htop (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/1730143 Title: no response to scroll wheel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/1730143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191259] Re: mplayer does not exit on end of file
Still doing this in Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191259 Title: mplayer does not exit on end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer2/+bug/1191259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191259] Re: mplayer does not exit on end of file
I take that back. I should have said this is happening in mplayer under Xenial, not mplayer2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191259 Title: mplayer does not exit on end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer2/+bug/1191259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
:( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207674] Re: Man page refers to "trash-restore" instead of "restore-trash"
And BTW, this is still the case in Xenial, 64 bit version. I wonder how many man-hours have been wasted by people trying to figure out how to use "trash-restore". Probably something under 1 in most individual cases, but how many cases are there? Surely not just the few that reached this page. Most probably either figured it out by reading at github or gave up before getting here. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207674 Title: Man page refers to "trash-restore" instead of "restore-trash" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trash-cli/+bug/1207674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207674] Re: Man page refers to "trash-restore" instead of "restore-trash"
According to Francia upstream, this IS a specific Ubuntu problem, because it was fixed upstream a while back. He says the version Ubuntu is using: " is very old, is from 2012, unfortunately seems that Ubuntu is still using a old version in its distribution. The current version is 0.17.1.14." from: https://github.com/andreafrancia/trash-cli/issues/101 So, no, it doesn't need a "patch" per se, unless I misunderstand the term, it just needs to be replaced with the current version instead of one 5 years old. ** Bug watch added: github.com/andreafrancia/trash-cli/issues #101 https://github.com/andreafrancia/trash-cli/issues/101 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207674 Title: Man page refers to "trash-restore" instead of "restore-trash" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trash-cli/+bug/1207674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Can somebody please tell where we can follow up the input maintainers? ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Hello! I also hope for a solution. Is there any place (@input maintainers) to track the effort/process of the bug? Thank's everybody to bringing thinks forward! Greetings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
But I can't boot stock ubuntu because I have a 32-bit bootloader and boot a 64-bit OS. (Intel Microsoft Atom Deal) For that reason I use isorespin.sh (http://linuxiumcomau.blogspot.com/) and use the latest mainlinekernel to be able to use networking (wifi) I can try respin without mainlinekernel - the question: How can I subbmit apport while have no networking working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.12.0-041200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1400463/+attachment/4900375/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1400463/+attachment/4900374/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
I did it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Kai-Heng Feng (kaihengfeng) wrote 4 hours ago: #9 Use ubuntu 17.04, and run `apport-collect 1400463`. I will try this at home! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
What can we do about/against it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Just digging out this 3-year old Thread to tell that this is still not fixed in 2017. Having these two Medion Notebooks: - Medion Akoya S2217 - Medion Akoya S2218 with the same Touchpad: - ITE Device(8910) Tested with: - ubuntu 16.04 - ubuntu 16.10 - ubuntu 17.04 And there is no: - Multitouch - Scrooling - other Features just plain pointing device (which makes live much harder!) Please tell what to do getting this one fixed one day Thank's for all the hard work! Greetings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691500] Re: synaptic as unpriveleged user crashes
It started working again. Not sure why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691500 Title: synaptic as unpriveleged user crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1691500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
Regards from Kaliningrad, Russia That bug is being fixed here partially by now, see below. Just to make sure, I visited some PC shops around and, to my surprise, found some computers with Ubuntu and few with FreeDOS (and, as consultant said, any linux distro from list could be installed for free). The fun is what some own Linux distro is used (AFAIK) by Russian Ministry of Internal Affairs, and there is military Rosa linux (totally shitty from what I heard but still). If only we could make schools to teach students to use Linux systems instead, that would change the game. I estimate the prevalence of free software in education here as about 15-18%, maybe 25% based on what I see in university. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1 Title: Microsoft has a majority market share To manage notifications about this bug go to: https://bugs.launchpad.net/clubdistro/+bug/1/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691500] [NEW] synaptic as unpriveleged user crashes
Public bug reported: I sometimes invoke synaptic as an plain user, just to browse and read the descriptions, etc. Used to work fine. Then I upgraded the kernel from 4.4.0-75 to 4.4.0-78 by installing linux-generic (it had been uninstalled to keep '77 at bay, because '77 killed my system). Everything seems to be fine on that score. New kernel boots fine and apt seems happy. But now syanaptic as plain user crashes. Started this way to log anything that mighgt be relevant: synaptic > synaptic_as_user_terminal_output.txt Got this in a pop up window: E: Could not open file /var/cache/apt/pkgcache.bin - open (2: No such file or directory) E: _cache->open() failed, please report. Then there was no synaptic gui and this was left in the visible terminal: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. The log file synaptic_as_user_terminal_output.txt is completely empty. This is on Xenial, 64 bit, a system built from the mini.iso, with xorg, xinit, and openbox. No other DE, per se, just plain openbox. The commands were run in xterm with PWD = ~/ Synaptic version is 0.83 ** Affects: synaptic (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/1691500 Title: synaptic as unpriveleged user crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1691500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353449] Re: lyx 1.6.x impossibly slow
I just saw [here](https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/129813) that this might be related to more general NVIDIA related X issues, that are [supposedly solved in the latest X 1.19](https://devtalk.nvidia.com/default/topic/976844/xorg-1-19-support/). I am on a fresh test install of Ubuntu 17.04 using the 340.102 driver now ([which supports X 1.19](https://www.phoronix.com/scan.php?page=news_item=NVIDIA- Legacy-6-Fermi-1.19))and confirm that lyx performance is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/353449 Title: lyx 1.6.x impossibly slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353449] Re: lyx 1.6.x impossibly slow
I am suffering from this bug too. While scrolling, Xorgs cpu usage increases (moderatly), while the process lyx uses 100% CPU. Scrolling too far causes the window to grey out, typing text becomes impossibly complicated due to the lag. None of the proposed fixes above changes anything for me ... @lyx-devs, is there anything I can do to provide tests that can help? This is breaking lyx usability for me, and it's not a piece of software I'd like to sacrifice with a shrug. Lyx 2.2.2 on Ubuntu 16.10 Xeon 3GHz Quadcore, 16 GB ram NVIDIA Quadro FX 5600 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/353449 Title: lyx 1.6.x impossibly slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/353449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present
Manually adding tmpfs /tmp tmpfs defaults 0 0 to fstab does seem to be a functional workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091792 Title: The disk drive for /tmp is not ready yet or not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091792] Re: The disk drive for /tmp is not ready yet or not present
I'm pretty sure I'm still seeing the on a up-to-date trusty install as well. This is in a rented dedicated server too, so it's extra spectacularly annoying, because I have to wait for someone to go press a key on the keyboard to fix it. mountall -v says "mountall 2.49" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091792 Title: The disk drive for /tmp is not ready yet or not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663198] [NEW] knode missing a dependency
Public bug reported: When installing KNode on Ubuntu 16.10 from the official repositories (version 4:4.14.10), it is not installing a required dependency: kde4pimlibs-kio-plugins Therefore KNode can't use the NNTP protocol and is useless. After manually installing kde4pimlibs-kio-plugins, the application works as expected. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663198 Title: knode missing a dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1663198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659140] Re: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)
** Tags added: security ** Tags removed: security ** Tags added: startx ** Tags added: security tty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659140 Title: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659140] Re: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)
There doesn't seem to be an "edit" button, so I'll add details in comments as I discover them. In the situation described, the same thing happens if I use the command "logout" instead of "exit". In the error messages put forth by X (I presume) in tty2 while it was crashing in tty1 because I had just done "logout" in tty2, there was an oddity - it stated the time and date and the date was one day behind but the time was correct. I'm in the +5 zone but I suffer a government of idiots and who insist I "save" daylight by setting my clock wrong. It was nominally 2 pm here, but any way you look at it the date was the same at Greenwich unless I'm sadly confused. Under X the date was and is correct. I've now restarted X in tty1 (where it was to begin with - that's where Xenial puts X, not in tty7 as in days of yore) an logged in again in tty2. I did su (I'm a naughty boy - I enabled su) in tty2 got a root prompt, and then entered the command "exit". It went back to a user prompt and did NOT crash X in tty1. So whether "exit" makes X crash depends on the circumstances. I haven't studied "exit" but apparently if I've logged in as user and do "su", exit merely logs out root on the tty. But if I do "exit" on a tty when I'm logged in as user it seems it does something more and that something more is something X doesn't like. It didn't work that way in Trusty. Now I'm wondering if this is properly an X bug, as opposed to a bug in whatever "logout" and "exit" call in common. Or maybe in bash itself. I'd appreciate an opinion as to whether I should report this against a different package. Later, I'll tinker more, and post the log when I find it. For now, for anyone else annoyed by this, my insecure work-around is simply not to log out of ttys but leave them logged in. This is a security problem if you are in an environment where you lock your kb/mouse/screen with something like xscreensaver or xtrlock in that a logged in tty provides an opportunity for an evil person to shut off your screen locker or just do damage from the command line. Not much of an issue for me at the moment. If this problem leads others to this obvious work-around though, I could argue that it is a security issue. So should this bug be flagged as such? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659140 Title: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659140] [NEW] x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)
Public bug reported: Observed behavior: When I get an alternate tty, or whatever it's called, with cntrl-alt-FN, where N is any digit, 2-6, inclusive; log in as the same user on the console; do stuff; and then log out with "exit": I'm suddenly back in tty1 and X has crashed. There is no x on any console. I can start it again with startx. Expected behavior: As it does in 14.04, I should just get a login prompt and stay in the same console. X running in tty1 should be unaffected, like x in tty7 would be unaffected in Trusty. This is 64 bit Xenial with a minimalist Openbox environment, built from the mini.iso. I start X with "startx". ** Affects: xorg (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/1659140 Title: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562219] Re: Unprivileged xinit wont start in unallocated vt
Uh, I wish I could edit my 2 posts above out. My problem was simple. After installing from the mini.iso, I was running an installation script that has a command of the form: sudo apt-get install --no-install-recommends package1 package2 package3 . . . It always worked before. But one of those packages no longer exists and apparently apt-get just doesn't anything on a list like that when ANY of them are missing. There was an error message but it only refered to the one package so I falsly assumed it was getting the others. So I didn't have openbox. Duh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: Unprivileged xinit wont start in unallocated vt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562219] Re: Unprivileged xinit wont start in unallocated vt
I should add that this probably the 5th or 6th time I've installed a 16.04 system on this machine and failed to get startx to work properly. I have another such that I haven't scrapped yet that WILL eventually start openbox in response to startx. But it takes a long time and results in my being logged in on ALL available ttys with most of them showing error messages about xserver failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: Unprivileged xinit wont start in unallocated vt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562219] Re: Unprivileged xinit wont start in unallocated vt
Me too. Under 16.04, 64 bit, with openbox, startx (or xinit) as user fails. Sudo startx gives me a console with a tiny font, so apparently it starts X but not Openbox. I'd explore that further and probably find how to start Openbox, but I don't want to run X as root anyway. I just tried sudo as a diagnostic experiment. I have another 16.04 64 bit system on the same machine using lighdm. That does boot and run openbox. That sys has OTHER problems I won't go into here, but it does prove the problem lies with xinit. Given all the OTHER problems with it, it also proves that 16.04 wasn't ready for release at all, let alone as an LTS. Maybe Canonical needs to reconsider the release-on-schedule policy and instead wait until they get through the alpha stage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: Unprivileged xinit wont start in unallocated vt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
confirmed "HandleLidSwitchDocked=suspend" worked for me. hp pavilion g6 Close lid, suspended and opening lid unsuspended automatially. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520979] Re: Grub multiboot is unable to load Xen under EFI
What part of this is "fixed"? Anyways, xen can apparently support efi-booting as a efi executable directly, but for some reason ubuntu doesn't ship the "xen.efi" (see https://wiki.xenproject.org/wiki/Xen_EFI)? While I understand that fixing this is kind of out of the scope of the ubuntu packager people, at least mark it "wontfix" or something. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520979 Title: Grub multiboot is unable to load Xen under EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1520979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645094] [NEW] package calculix-ccx (not installed) failed to install/upgrade: próba nadpisania "/usr/bin/ccx", który istnieje także w pakiecie ccx 2.7-1ppa2~trusty1
Public bug reported: no ProblemType: Package DistroRelease: Ubuntu 16.04 Package: calculix-ccx (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 27 13:49:37 2016 DpkgTerminalLog: Przygotowywanie do rozpakowania pakietu .../calculix-ccx_2.9-1_amd64.deb ... Rozpakowywanie pakietu calculix-ccx (2.9-1) ... dpkg: błąd przetwarzania archiwum /var/cache/apt/archives/calculix-ccx_2.9-1_amd64.deb (--unpack): próba nadpisania "/usr/bin/ccx", który istnieje także w pakiecie ccx 2.7-1ppa2~trusty1 ErrorMessage: próba nadpisania "/usr/bin/ccx", który istnieje także w pakiecie ccx 2.7-1ppa2~trusty1 InstallationDate: Installed on 2015-01-20 (676 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: calculix-ccx Title: package calculix-ccx (not installed) failed to install/upgrade: próba nadpisania "/usr/bin/ccx", który istnieje także w pakiecie ccx 2.7-1ppa2~trusty1 UpgradeStatus: Upgraded to xenial on 2016-11-27 (0 days ago) ** Affects: calculix-ccx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645094 Title: package calculix-ccx (not installed) failed to install/upgrade: próba nadpisania "/usr/bin/ccx", który istnieje także w pakiecie ccx 2.7-1ppa2~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calculix-ccx/+bug/1645094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639951] [NEW] Installation could not restore prevously-installed applications
Public bug reported: I was using firefox ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: KDE Date: Mon Nov 7 23:00:49 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu ubiquity-2.21.63.2 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639951 Title: Installation could not restore prevously-installed applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1639951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625701] [NEW] file-roller doesn't use gzip/tar default options
Public bug reported: Ubuntu 16.04 Normally using tar with gzip (tar cvzf file.tgz files) will store symlinks, but not follow them, but file-roller follows symlinks and unexpectedly compresses all link targets along with the other data. Please restore file-roller to use the default compression options. ** Affects: file-roller (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/1625701 Title: file-roller doesn't use gzip/tar default options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1625701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625119] [NEW] Nvidia settings can't be saved
Public bug reported: Ubuntu 16.04 suggest proprietary Nvidia drivers when a Nvidia GPU is present. The settings in the nvidia-settings tool cannot be saved, however, without starting the tool as root and doing all kinds of workarounds which is impossible to do for the average user. Do you really expect users to reconfigure their displays after every login? Unless you can fix this, the Nvidia driver recommendation should simply be removed. Delivering such a horrible experience to millions of users seems like a bad joke and the persons responsible should feel really bad about this. Ubuntu has no future anywhere with such usability issues. ** Affects: nvidia-settings (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/1625119 Title: Nvidia settings can't be saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1625119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429620] Re: where is the ntpctl command?
Pardon my stupidity. ntpdate -q meets my need fine. So does downloading the time from any server that posts a continually updated value of "now". See: https://superuser.com/questions/635020/how-to-know-current-time-from-internet-from-command-line-in-linux So I have my work-around. It's still true, as far as I can see, that this bug is still unfixed in Trusty, but "ntpdate -q" is quite sufficient to put suspenders on my ntpd time traveler's navigation belt. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429620 Title: where is the ntpctl command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/1429620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429620] Re: where is the ntpctl command?
Mea culpa for redundant post. I entered it on a different page & didn't realize it would wind up here anyway. And 8 was correct, not 9. I'd at least edit it out, but I see no button for that. BTW, unless and until this is fixed, anybody got a workaround for querying to see how accurate the present time is without confusing openntpd? +- 5 seconds is good enough for me, probably even +- 30 seconds would be ok, but recently I've occasionally had times that were off considerably more than that. I THINK that is because I didn't have ANY ntpd-like thing installed, just ntpdate. So that problem is probably corrected now, but still I have some scripts where I log a time and I'd like to add a check to make sure I can count on some minimal level of accuracy at the time I log it. Thanks for reading. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429620 Title: where is the ntpctl command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/1429620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429620] Re: where is the ntpctl command?
"fix released" was 9 months ago and this still affects Trusty, which is LTS with 3 years to go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429620 Title: where is the ntpctl command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/1429620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429620] Re: where is the ntpctl command?
"status:Confirmed → Fix Released" What's that mean exactly? It's 8 months since the preceding post and it isn't fixed in 14.04 LTS as of 2016 September 12. Is it going to be, or is Trusty abandoned, despite being LTS with 3 years to go before EOL? How soon is "soon"? Is it fixed in 16.04? I'll abandon Trusty as soon as I can get my Conky to work in 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429620 Title: where is the ntpctl command? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openntpd/+bug/1429620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525735] Re: X server fails to start under regular user in Xenial
Mea culpa. I think I had 2 different (albeit similar) bug reports open in different tabs and posted to the wrong one. FWIW, the proximate cause of my problem was simple: ~/.Xauthority was owned root:root. That seems to me to be an installer bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525735 Title: X server fails to start under regular user in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1525735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525735] Re: X server fails to start under regular user in Xenial
I should have mentioned that the system shows a lot of large print output in tty 7 as the system is booting and hangs at "started update UTMP about system runlevel changes." When I look in tty1 there is screenful of stuff and then a prompt, looking as if it had successfully booted. I can log in there and all is normal except only root can start x. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525735 Title: X server fails to start under regular user in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1525735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525735] Re: X server fails to start under regular user in Xenial
Me too. Fresh install of 16.04 from the mini.iso. Used apt-get to install xorg, openbox and some applications. This always used to work. Now only root can start x. This is bare metal, not virtual. I tried installing first xserver-xorg-video-all and then xserver-xorg-legacy. Neither made any difference. This is a Samsung rv515 "laptop" (I'd say notebook). I can't understand why this is marked low priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525735 Title: X server fails to start under regular user in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1525735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619634] [NEW] plymouthd crashed with SIGSEGV in ply_renderer_get_input_source()
Public bug reported: I get this crash report almost every time I boot for a very long time in Ubuntu 16.04 since I installed GNOME. DistroRelease: Ubuntu 16.04 Architecture: i386 Package: plymouth 0.9.2-3ubuntu13.1 Anyone who has the same problem or has a solution for this crash, please comment. ** Affects: plymouth (Ubuntu) Importance: Undecided Assignee: Implying I have a name (mlaseca95) Status: New ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) => Implying I have a name (mlaseca95) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619634 Title: plymouthd crashed with SIGSEGV in ply_renderer_get_input_source() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1619634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554307] Re: linux-boot-prober yields wrong uuid for kernel root parameter
Thanks, EvilSupahFly. I can now add this:
Rm'ing every grub related file on the other systems, reinstalling grub,
and running update-grub was REALLY BAD IDEA. Now when I try to boot
/dev/sda6 (the system that is an fsarchiver-made clone of my main,
/dev/sda5-based 14.04 system, where grub is supposed to live) all I get
is BusyBox with a prompt something like "[initramfs]". So now my sda5
system is broken. But I can restore the fsa backup again easily enough.
It is possible, AFAIK from my own ignorance, that a modified approach
like that MIGHT work, if you knew exactly WHICH grub related files to
rm, and if anyone thinks that's the case, I'd appreciate their expanding
on the topic, as it sounds to me as if, that if something like that
would work at all it might be either something I'd only have to do once,
or failing that, something that might be simple enough to write a script
to do, and run that script every time I run dist-upgrade or restore an
fsarchiver backup to a partition it wasn't on originally.
When you say manual editing works for you, I assume you mean editing
grub.cfg on the system that should be the one where grub was last
installed via a regular installation procedure (as opposed to restoring
a clone with fsarchiver or Clonezilla). As for update-grub rewriting it
incorrectly, I could just mark it read-only or take the x perm off
update-grub, or alias update-grub to something innocuous. As for
grub.cfg getting outdated and booting old kernels (or crashing if
they've been removed), I seem to remember there is some way to make an
entry that in effect says "boot from the latest one there, whatever it
is". If I had a grub.cfg like that, could I just disable os-prober and
update-grub, and not have to edit until I changed my partition setup?
Would having a seperate boot partition get me around all this and let
grub work automatically?
If I have to manually edit grub.cfg every time a kernel is updated, or
every time I install an OS or restore an fsa or clonezilla backup, would
I be better off switching to a boot loader that was written with the
INTENT that a boot configuration file would have to be manually
maintained?
I've also tried the LILO approach since I posted. It does boot my main
/dev/sda5 14.04 fine, but it didn't pick up on any of the other systems
automatically. So I purged it with apt-get and reinstalled grub ("grub
'2'") hoping I could get find the magic spell to make grub-2 work
automatically, but so far I haven't. So, if I DO have to hand edit every
time constantly, maybe I should revert that.
At any rate, anyone reading this looking for work arounds will now know
at least one thing that does NOT work. Anyone with thoughts on how to
set up a low maintenance boot loader, either with grub-2 or something
else, that can cope with new OSs coming and going through normal
installation and clone restoration, please share your ideas.
Meanwhile, I think I'm going to read up on boot partitions. Thanks for
reading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/554307/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554307] Re: linux-boot-prober yields wrong uuid for kernel root parameter
BTW, all my linux systems are 1-partition-each, no seperate ~s, or swaps or boot. Keeping it simple. They are on 2 drives, one external, one internal. Grub is on /dev/sda with config files on sda5, which is the one that boots. Some are on primary and some on logical partitions. Sda1 and sda2 are Win-7. I have maybe 7 'nix systems, most but not all of which are 14.04s. And this happened after I defragged the W7 and shrunk its main partition (sda2)(what a collasol PITA - MS makes that hard deliberately, the farstards), put in a new sda6, restored an fsarchiver backup of sda5 to it, reset it to a new UUID, and did update-grub. When it didn't work, I used all the native tools to purge grub* and reinstall. dpkg kept returning errors which I couldn't fix with any dpkg or apt-get commands, despite hours of trying. To my surprise Synaptic had no trouble fixing that. But no matter how many times I purge and reinstall, it is the same issue now. One more work-around I just thought of, in light of some of the comments above, that may be worth trying: -After purging grub* and manually rm'ing any grub related files I can find on the system that installed grub to sda, which I already tried, go on and rm any grub related files I can fine on ALL partitions before reinstalling. Maybe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/554307 Title: linux-boot-prober yields wrong uuid for kernel root parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/554307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 554307] Re: linux-boot-prober yields wrong uuid for kernel root parameter
Same thing with me in 14.04. This is a pretty basic thing to be broken for so long. Suggestions for work-arounds would be nice, since it doesn't look fixing it is imminent. Personally, I've tried a 2 grub rescue utilities, one from within one of the partitions that will boot, and another from CD. Neither worked. I'm downloading 2 more to burn optical disks with, but I'm not hopeful. So maybe: -Edit grub.cfg by hand, or is there a better file to edit? -Roll back to legacy, which was pretty darn stable and foolproof? -Switch LILO? -Switch to some exotic loader (isn't there a "Burg"?)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/554307 Title: linux-boot-prober yields wrong uuid for kernel root parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/554307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333630] Re: screen caught signal 11 core dumped
@martin.von.wittich - Get used to pulling screen sources and compiling it yourself. No one at ubuntu has any interest in actually supporting their "supported" OS. It's fortunately pretty easy to build a non-fucked version of screen: - `apt-get install build-essential ncurses-dev` to get the dependencies. - Grab the latest from http://ftp.gnu.org/gnu/screen/ (currently screen-4.3.1.tar.gz) - `tar -xvf screen-4.3.1.tar.gz && cd screen-4.3.1 && ./configure && make -j4 && sudo make install` will make and install a version of screen without 2 year old game breaking bugs. Then, you just have to make sure you don't accidentally let the "SUPPORTED" broken version get installed, because it can clobber the manual version that actually doesn't periodically kill all your processes, because fuck bothering to actually fix things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333630 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/screen/+bug/1333630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511735] Re: libnl: fail to bind() netlink sockets
It affect my 14.04.1 system WITHOUT trusty-proposed enabled. FYI: kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581535] Re: libnl upgrade breaks Network Manager
*** This bug is a duplicate of bug 1511735 *** https://bugs.launchpad.net/bugs/1511735 As Jon B mentions in comment #9 above, even I DO NOT have trusty- proposed enabled on my 14.04.1 with kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581535 Title: libnl upgrade breaks Network Manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991638] Re: Crashes when gui is invoked
Same thing in 64 bit Ubuntu 14.04 under plain Openbox. Any workarounds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991638 Title: Crashes when gui is invoked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imwheel/+bug/991638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004812] Re: imwheel -c segfaults
*** This bug is a duplicate of bug 991638 *** https://bugs.launchpad.net/bugs/991638 Same thing in 64 bit Ubuntu 14.04 under plain Openbox. Any workarounds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004812 Title: imwheel -c segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imwheel/+bug/1004812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573097] Re: upgrade to 16.04 failed, hash sum mismatch
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573097 Title: upgrade to 16.04 failed, hash sum mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1573097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573097] [NEW] upgrade to 16.04 failed, hash sum mismatch
Public bug reported: Tried to upgrade from 14.04.4 LTS to 16.04. (Date: 21.04.2016) upgrading via 'do-release-upgrade -d' failed and ended with the following message: (Im using a german version) "W:Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/xenial/universe/source/Sources Hash-Summe stimmt nicht überein , E:Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. " (translation (kinda :) )) "W:Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/universe/source/Sources hash sum mismatch, E: Some index files failed to download. They have been ignored, or old ones used instead." This error was also discovered with the dash-upgrader ** Affects: ubuntu-release-upgrader (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/1573097 Title: upgrade to 16.04 failed, hash sum mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1573097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562658] Re: screen caught signal 11 core dumped
*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630 The original bug report was "The version of screen in X has a (serious) issue". The "response" was "Ok, we fixed it in Y". The version in X, where the problem was originally encountered is still broken and unfixed. Despite this fact, the bug report was closed. I don't know how you can consider that fixed. If Launchpad defines "Ubuntu" to be "only the latest version of ubuntu and not any of the LTS versions", well... ok? I don't think that definition is going to be too widely agreed on anywhere else, where "ubuntu" means all the OS releases. > No. Someone with the proper permissions (neither you nor I have them) > needs to explicitly mark the bug report as affecting 14.04 LTS and > open it for that release only. I won't poke those people, so it's up > to you to contact them. See the links I posted in my previous comment > for how to do that. Is that not the EXPLICIT purpose of this ENTIRE bug tracker? To let the appropriate people know that there is, I dunno, a bug? There is an *specific* category for *just* this *one* piece of software. WTF is the "Screen on Ubuntu" bug tracker for if NOT telling the people involved in managing the screen package on Ubuntu that there is a problem? Furthermore, the *original* bug was explicitly described as occurring on 14.04, so there has never been, as far as I'm aware, the contention that it affected any *other* platform. --- As an aside, from the "7.2. Stable Release Updates" subheading on that page: > We also allow updates to releases where a package has a high impact bug such > as > a severe regression from a previous release or a bug which could cause data > loss. > Due to the potential for such updates to themselves introduce bugs we only > allow > this where the change can be easily understood and verified. I have *personally* had data loss from this bug, due to screen eating all my processes when doing interactive data processing and having screen segfault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562658 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1562658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562658] Re: screen caught signal 11 core dumped
*** This bug is a duplicate of bug 1333630 *** https://bugs.launchpad.net/bugs/1333630 If you want to mark this as a duplicate, that's fine, but at least re- open the old bug. Until that's done, this is *not* a duplicate, the reporting issue has not been solved (hey look, that's for 14.04 too!). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562658 Title: screen caught signal 11 core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1562658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
