[Touch-packages] [Bug 1577042] Re: SIGSEGV in SoundTouch 1.9.2
** Package changed: ubuntu => soundtouch (Ubuntu) ** Changed in: soundtouch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1577042 Title: SIGSEGV in SoundTouch 1.9.2 Status in Mixxx: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: OS: Fedora 23 x86_64 Lib: soundtouch-1.9.2-3.fc23.x86_64 Branch: master (2.1.0-alpha-pre x64) Key Lock enabled Pitch at 0.00 - not moved during the whole session (AutoDJ background music @home) File plays fine after restart - same results - waveform generation is skipped now Warning [AnalyzerQueue 1]: Recoverable MP3 frame decoding error: lost synchronization Debug [AnalyzerQueue 1]: Waveform generation for track 92614 done 6 s Debug [AnalyzerQueue 1]: ReplayGain 2.0 (libebur128) result is -2.78099 dB for "/home/uk/Music/Collection/nico/chelsea girl/01-02 nico these days.mp3" Debug [AnalyzerQueue 1]: Beat Calculation complete Debug [AnalyzerQueue 1]: Key Detection complete Debug [AnalyzerQueue 1]: Key Histogram Debug [AnalyzerQueue 1]: 6 : "F" 7.93267e+06 Debug [AnalyzerQueue 1]: 11 : "B♭" 1.47456e+06 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffee22d2700 (LWP 16845)] 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () from /usr/lib64/libSoundTouch.so.1 (gdb) bt #0 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () at /usr/lib64/libSoundTouch.so.1 #1 0x77893037 in soundtouch::TDStretch::processSamples() () at /usr/lib64/libSoundTouch.so.1 #2 0x77891490 in soundtouch::SoundTouch::putSamples(float const*, unsigned int) () at /usr/lib64/libSoundTouch.so.1 #3 0x007cfc82 in EngineBufferScaleST::getScaled(float*, int) (this=0x20a9d00, pOutput=, buf_size=2048) at src/engine/enginebufferscalest.cpp:164 #4 0x007cba11 in EngineBuffer::process(float*, int) (this=0x1fa1be0, pOutput=0x7fffc8792010, iBufferSize=2048) at src/engine/enginebuffer.cpp:983 #5 0x007d1310 in EngineDeck::process(float*, int) (this=0x1f759d0, pOut=0x7fffc8792010, iBufferSize=2048) at src/engine/enginedeck.cpp:98 #6 0x007dff4e in EngineMaster::processChannels(int) (this=this@entry=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:318 #7 0x007e8b50 in EngineMaster::process(int) (this=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:350 #8 0x00b47d5b in SoundManager::onDeviceOutputCallback(unsigned int) (this=, iFramesPerBuffer=iFramesPerBuffer@entry=1024) at src/soundio/soundmanager.cpp:548 #9 0x00b44a36 in SoundDevicePortAudio::callbackProcessClkRef(unsigned int, float*, float const*, PaStreamCallbackTimeInfo const*, unsigned long) (this=0x1e337c0, framesPerBuffer=1024, out=0x4de4f2a0, in=, timeInfo= to continue, or q to quit--- ptimized out>, statusFlags=) at src/soundio/sounddeviceportaudio.cpp:949 #10 0x77459454 in AdaptingOutputOnlyProcess () at /usr/lib64/libportaudio.so.2 #11 0x7745aded in PaUtil_EndBufferProcessing () at /usr/lib64/libportaudio.so.2 #12 0x7746391b in CallbackThreadFunc () at /usr/lib64/libportaudio.so.2 #13 0x71d1e60a in start_thread () at /usr/lib64/libpthread.so.0 #14 0x7fffeeeb5a4d in clone () at /usr/lib64/libc.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1577042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577042] Re: SIGSEGV in SoundTouch 1.9.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: soundtouch (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. https://bugs.launchpad.net/bugs/1577042 Title: SIGSEGV in SoundTouch 1.9.2 Status in Mixxx: Confirmed Status in soundtouch package in Ubuntu: Confirmed Bug description: OS: Fedora 23 x86_64 Lib: soundtouch-1.9.2-3.fc23.x86_64 Branch: master (2.1.0-alpha-pre x64) Key Lock enabled Pitch at 0.00 - not moved during the whole session (AutoDJ background music @home) File plays fine after restart - same results - waveform generation is skipped now Warning [AnalyzerQueue 1]: Recoverable MP3 frame decoding error: lost synchronization Debug [AnalyzerQueue 1]: Waveform generation for track 92614 done 6 s Debug [AnalyzerQueue 1]: ReplayGain 2.0 (libebur128) result is -2.78099 dB for "/home/uk/Music/Collection/nico/chelsea girl/01-02 nico these days.mp3" Debug [AnalyzerQueue 1]: Beat Calculation complete Debug [AnalyzerQueue 1]: Key Detection complete Debug [AnalyzerQueue 1]: Key Histogram Debug [AnalyzerQueue 1]: 6 : "F" 7.93267e+06 Debug [AnalyzerQueue 1]: 11 : "B♭" 1.47456e+06 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffee22d2700 (LWP 16845)] 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () from /usr/lib64/libSoundTouch.so.1 (gdb) bt #0 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () at /usr/lib64/libSoundTouch.so.1 #1 0x77893037 in soundtouch::TDStretch::processSamples() () at /usr/lib64/libSoundTouch.so.1 #2 0x77891490 in soundtouch::SoundTouch::putSamples(float const*, unsigned int) () at /usr/lib64/libSoundTouch.so.1 #3 0x007cfc82 in EngineBufferScaleST::getScaled(float*, int) (this=0x20a9d00, pOutput=, buf_size=2048) at src/engine/enginebufferscalest.cpp:164 #4 0x007cba11 in EngineBuffer::process(float*, int) (this=0x1fa1be0, pOutput=0x7fffc8792010, iBufferSize=2048) at src/engine/enginebuffer.cpp:983 #5 0x007d1310 in EngineDeck::process(float*, int) (this=0x1f759d0, pOut=0x7fffc8792010, iBufferSize=2048) at src/engine/enginedeck.cpp:98 #6 0x007dff4e in EngineMaster::processChannels(int) (this=this@entry=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:318 #7 0x007e8b50 in EngineMaster::process(int) (this=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:350 #8 0x00b47d5b in SoundManager::onDeviceOutputCallback(unsigned int) (this=, iFramesPerBuffer=iFramesPerBuffer@entry=1024) at src/soundio/soundmanager.cpp:548 #9 0x00b44a36 in SoundDevicePortAudio::callbackProcessClkRef(unsigned int, float*, float const*, PaStreamCallbackTimeInfo const*, unsigned long) (this=0x1e337c0, framesPerBuffer=1024, out=0x4de4f2a0, in=, timeInfo= to continue, or q to quit--- ptimized out>, statusFlags=) at src/soundio/sounddeviceportaudio.cpp:949 #10 0x77459454 in AdaptingOutputOnlyProcess () at /usr/lib64/libportaudio.so.2 #11 0x7745aded in PaUtil_EndBufferProcessing () at /usr/lib64/libportaudio.so.2 #12 0x7746391b in CallbackThreadFunc () at /usr/lib64/libportaudio.so.2 #13 0x71d1e60a in start_thread () at /usr/lib64/libpthread.so.0 #14 0x7fffeeeb5a4d in clone () at /usr/lib64/libc.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1577042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577042] [NEW] SIGSEGV in SoundTouch 1.9.2
You have been subscribed to a public bug: OS: Fedora 23 x86_64 Lib: soundtouch-1.9.2-3.fc23.x86_64 Branch: master (2.1.0-alpha-pre x64) Key Lock enabled Pitch at 0.00 - not moved during the whole session (AutoDJ background music @home) File plays fine after restart - same results - waveform generation is skipped now Warning [AnalyzerQueue 1]: Recoverable MP3 frame decoding error: lost synchronization Debug [AnalyzerQueue 1]: Waveform generation for track 92614 done 6 s Debug [AnalyzerQueue 1]: ReplayGain 2.0 (libebur128) result is -2.78099 dB for "/home/uk/Music/Collection/nico/chelsea girl/01-02 nico these days.mp3" Debug [AnalyzerQueue 1]: Beat Calculation complete Debug [AnalyzerQueue 1]: Key Detection complete Debug [AnalyzerQueue 1]: Key Histogram Debug [AnalyzerQueue 1]: 6 : "F" 7.93267e+06 Debug [AnalyzerQueue 1]: 11 : "B♭" 1.47456e+06 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffee22d2700 (LWP 16845)] 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () from /usr/lib64/libSoundTouch.so.1 (gdb) bt #0 0x77891e90 in soundtouch::TDStretch::overlapStereo(float*, float const*) const () at /usr/lib64/libSoundTouch.so.1 #1 0x77893037 in soundtouch::TDStretch::processSamples() () at /usr/lib64/libSoundTouch.so.1 #2 0x77891490 in soundtouch::SoundTouch::putSamples(float const*, unsigned int) () at /usr/lib64/libSoundTouch.so.1 #3 0x007cfc82 in EngineBufferScaleST::getScaled(float*, int) (this=0x20a9d00, pOutput=, buf_size=2048) at src/engine/enginebufferscalest.cpp:164 #4 0x007cba11 in EngineBuffer::process(float*, int) (this=0x1fa1be0, pOutput=0x7fffc8792010, iBufferSize=2048) at src/engine/enginebuffer.cpp:983 #5 0x007d1310 in EngineDeck::process(float*, int) (this=0x1f759d0, pOut=0x7fffc8792010, iBufferSize=2048) at src/engine/enginedeck.cpp:98 #6 0x007dff4e in EngineMaster::processChannels(int) (this=this@entry=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:318 #7 0x007e8b50 in EngineMaster::process(int) (this=0x14fe100, iBufferSize=iBufferSize@entry=2048) at src/engine/enginemaster.cpp:350 #8 0x00b47d5b in SoundManager::onDeviceOutputCallback(unsigned int) (this=, iFramesPerBuffer=iFramesPerBuffer@entry=1024) at src/soundio/soundmanager.cpp:548 #9 0x00b44a36 in SoundDevicePortAudio::callbackProcessClkRef(unsigned int, float*, float const*, PaStreamCallbackTimeInfo const*, unsigned long) (this=0x1e337c0, framesPerBuffer=1024, out=0x4de4f2a0, in=, timeInfo= to continue, or q to quit--- ptimized out>, statusFlags=) at src/soundio/sounddeviceportaudio.cpp:949 #10 0x77459454 in AdaptingOutputOnlyProcess () at /usr/lib64/libportaudio.so.2 #11 0x7745aded in PaUtil_EndBufferProcessing () at /usr/lib64/libportaudio.so.2 #12 0x7746391b in CallbackThreadFunc () at /usr/lib64/libportaudio.so.2 #13 0x71d1e60a in start_thread () at /usr/lib64/libpthread.so.0 #14 0x7fffeeeb5a4d in clone () at /usr/lib64/libc.so.6 ** Affects: mixxx Importance: Critical Status: Confirmed ** Affects: soundtouch (Ubuntu) Importance: Undecided Status: Confirmed -- SIGSEGV in SoundTouch 1.9.2 https://bugs.launchpad.net/bugs/1577042 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to soundtouch in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
This is a text-only installation, and I cannot seem to login to launchpad via a text browser (error: "bad robot go away"). Is there another way I can provide the information needed? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
FYI systemd-tmpfiles command running when installing or upgrading systemd is in debhelper pkg cat autoscripts/postinst-init-tmpfiles if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then # In case this system is running systemd, we need to ensure that all # necessary tmpfiles (if any) are created before starting. if [ -d /run/systemd/system ] ; then systemd-tmpfiles --create #TMPFILES# >/dev/null || true fi fi #TMPFILES# has list of tmpfiles conf file owned by systemd only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: New Status in systemd source package in Xenial: New Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: New Status in systemd source package in Artful: New Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so
[Touch-packages] [Bug 1671952] Re: python program gets segmentation fault
[Expired for python3-defaults (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python3-defaults (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1671952 Title: python program gets segmentation fault Status in python3-defaults package in Ubuntu: Expired Bug description: Running a Python 3 / sqlite3 script that develops a database representing a game tree, a segmentation fault occurred. The program had written 4,910,495 lines of output when it crashed, redirected to a file. It appears normal, and its size is about right for the job being performed. There's nothing suspicious at the end. This is a hobby project, so I can share the entire database and any of the code you need, but much of it is included in the screen-scraped console session attached herewith. In particular: - the command-line - a gdb stack backtrace of the core dump - the program being run - a run of the sqlite3 "pragma integrity_check" that shows the database is sound - database .schema output CPU is Core i-7, 32 GB RAM. Code is recursive, but limited by the nature of the problem and parameters to depth of about 10 calls. Code has been used before, albeit on a problem with smaller recursive depth and shorter expected run-time. db is 18GB on a 12TB RAID partition; plenty of space kernel is X86-64 4.4.0-66-generic un-fooled-around-with Python and the sqlite3 package is 3.5.2, straight from the repositories I have a backup of the database right after this crash (being performed as I write this) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 10 13:47:54 2017 InstallationDate: Installed on 2016-08-08 (214 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1671952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702459] Re: Failed to send request: 'str' object has no attribute 'decode' on Ubuntu 16.04
[Expired for python3-defaults (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: python3-defaults (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1702459
Title:
Failed to send request: 'str' object has no attribute 'decode' on
Ubuntu 16.04
Status in python3-defaults package in Ubuntu:
Expired
Bug description:
The code attached below generates an error on Ubuntu 16.04 LTS with
python3 default package installed (python3 --version returns 3.5.2).
The error message is:
«Failed to send request: 'str' object has no attribute 'decode'»
The code works fine on Ubuntu 17.04 and Fedora 25 (both python3 --version
returning 3.5.3). The code also runs on Ubuntu 16.04 LTS with self-compiled
from source python 3.6.1.
Also, the code has been running ok for over a year on Ubuntu 16.04 LTS - it
only fails since mid June 2017.
Not sure where the issue is, probably in Ubuntu package for python or in
python version 3.5.2.
from datetime import datetime,date,time,timezone
import tweepy as twitter
def sendToTwitter():
consumer_key='...'
consumer_secret='...'
access_token_key='...'
access_token_secret='..'
#connect to the twitter api
message = "tweet test"
print("trying to send the tweet...")
try:
auth = twitter.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_token_key, access_token_secret)
api = twitter.API(auth)
status = api.update_status(status=message)
print("tweet sent")
except Exception as e:
print("error while tweeting. reason : " + str(e))
return
sendToTwitter()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1702459/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time
This bug was fixed in the package libxkbcommon - 0.8.0-2 --- libxkbcommon (0.8.0-2) unstable; urgency=medium * control: Mark -dev packages M-A: same. (LP: #1772512) * Split documentation from -dev to -doc. (Closes: #893855) * rules: Purge doxygen .md5 files. -- Timo Aaltonen Thu, 24 May 2018 16:59:28 +0300 ** Changed in: libxkbcommon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Bug description: Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1775499] Re: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
thanks On Thu, Jun 7, 2018 at 11:40 AM, Apport retracing service < 1775...@bugs.launchpad.net> wrote: > ** Tags removed: need-duplicate-check > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1775499 > > Title: > package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to > install/upgrade: package is in a very bad inconsistent state; you > should reinstall it before attempting configuration > > Status in libhybris package in Ubuntu: > New > > Bug description: > always got problem, > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 > ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 > Uname: Linux 4.4.0-121-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > Date: Thu Jun 7 11:30:49 2018 > Dependencies: >gcc-6-base 6.0.1-0ubuntu1 >libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7 >libc6 2.23-0ubuntu10 >libgcc1 1:6.0.1-0ubuntu1 >libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7 > DuplicateSignature: >package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7 >Processing triggers for doc-base (0.10.7) ... >Processing 1 changed doc-base file... >dpkg: error processing package libhardware2 (--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 2018-01-26 (132 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.1 >apt 1.2.15ubuntu0.2 > SourcePackage: libhybris > Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/ > 1775499/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1775499 Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libhybris package in Ubuntu: New Bug description: always got problem, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 7 11:30:49 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7 DuplicateSignature: package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libhardware2 (--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 2018-01-26 (132 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: libhybris Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1775499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775499] Re: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1775499 Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libhybris package in Ubuntu: New Bug description: always got problem, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 7 11:30:49 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7 DuplicateSignature: package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libhardware2 (--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 2018-01-26 (132 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: libhybris Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1775499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775499] [NEW] package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att
Public bug reported: always got problem, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 7 11:30:49 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7 DuplicateSignature: package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libhardware2 (--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 2018-01-26 (132 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: libhybris Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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: libhybris (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1775499 Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libhybris package in Ubuntu: New Bug description: always got problem, ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 7 11:30:49 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libandroid-properties1 0.1.0+git20151016+6d424c9-0ubuntu7 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libhybris-common1 0.1.0+git20151016+6d424c9-0ubuntu7 DuplicateSignature: package:libhardware2:0.1.0+git20151016+6d424c9-0ubuntu7 Processing triggers for doc-base (0.10.7) ... Processing 1 changed doc-base file... dpkg: error processing package libhardware2 (--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 2018-01-26 (132 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: libhybris Title: package libhardware2 0.1.0+git20151016+6d424c9-0ubuntu7 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1775499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
*** This bug is a duplicate of bug 1698270 *** https://bugs.launchpad.net/bugs/1698270 Charlie, yes I would recommend using mpv instead of totem. mpv will perform better and is the only other video player that will take advantage of Intel hardware acceleration properly [2]. I do _not_ recommend gnome-mpv [1] and also do _not_ recommend vlc because it seems to be lacking in hardware acceleration. I have no experience with SMPlayer, but please see also [2]. Tracy, the mpv close issue is bug 1720835. I think we should merge this into bug 1698270 now. [1] https://community.ubuntu.com/t/hardware-accelerated-video-playback/304/4 [2] https://wiki.ubuntu.com/IntelQuickSyncVideo ** This bug has been marked a duplicate of bug 1698270 Totem pauses and stutters during video playback even when CPU usage is low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
[Touch-packages] [Bug 1775230] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1775230 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
BTW, the following shows up in the terminal output for mpv under Wayland (I don't recall seeing this under Xorg) [vo/opengl] retrieving framebuffer depth: OpenGL error INVALID_OPERATION. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
In response to my previous comment, switching to SMPlayer improves the symptom, but does not seem to resolve it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
Sorry for the long delay in responding - had to wait for some other things to finish so I could switch from Xorg to Wayland. The same types of pauses/lags/freezes happen to me under Wayland using mpv as were happening under Xorg. They may be slightly less frequent (subjective judgment, no actual counts done), but they still occur. Also, I find that I am unable to close mpv under Wayland. Alt-F4 does nothing, nor does going to the Window menu and choosing Quit. The video continues, and I am not sure exactly what else to use to close it (other than just waiting for it to finish running) - I don't know much about mpv. Closing wasn't a problem under Xorg - either of the two methods mentioned above worked there. Just throwing that out there for consideration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel
[Touch-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
If I am reading this commentary, and that in https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/1698270 it's looking like uninstalling totem and changing to another player might be the best answer, am I correct? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich
[Touch-packages] [Bug 1775452] Re: Nvidia problems
It sounds like you're reporting a problem with the nouveau driver. Unfortunately the attached logs don't show the "flood" you refer to. Please copy and paste an example of the message flood. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Nvidia problems + Nouveau problems ** Tags added: nouveau -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775452 Title: Nouveau problems Status in linux package in Ubuntu: Incomplete Bug description: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
This bug has been reported with both GF106 (bug 1775279) and GM107GLM (this bug) hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 18.04(Updated 30.03.2018) System Language: Turkish Please check screenshots --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775429] Re: Label in stackswitcher button is not bold when selected
** Also affects: ubuntu-themes Importance: Undecided Status: New ** Tags added: visual-quality -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775429 Title: Label in stackswitcher button is not bold when selected Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775432] Re: Stackswitcher buttons in gnome-software are not themed alike
** Also affects: ubuntu-themes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
Before we merge this bug into bug 1698270 I would like to hear Tracy's response to comment #25. Then I expect we will need/want to get more of the above lists of gnome- shell performance issues fixed before we can confidently say this issue exists purely within video playback. P.S. If the problem is purely a video playback issue then my suspicion is that some component is implementing frame dropping incorrectly. If it is implemented using double buffers then you can easily starve the screen of new frames while repeatedly (racily) replacing the backbuffer. The right approach then is to use 3 buffers and the mailbox algorithm. The mailbox algorithm is nothing new, but that's what Vulkan calls it anyway: https://software.intel.com/en-us/articles/api-without-secrets- introduction-to-vulkan-part-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
Sergei, "performance" is a general category of problems that includes dropped frames. For example, in gnome-shell I have separated those issues: https://trello.com/c/Q6JYXPPs from the ones that incur measurably high hardware usage: https://trello.com/c/pe5mRmx7 A low frame rate is still a performance problem even if it's not stressing the hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem:
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
I agree and have already proposed the solution you describe: https://trello.com/c/aI3BX3ax -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
** Changed in: ubuntu-themes
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775488] [NEW] Ubuntu adm Firefox freezing 2 much
Private bug reported: This make me nervous! Often the system hangs and freezes ... I do not know what I'm doing anymore. Could it be a little memory? If you can, can you give me a hand? thanks a lot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 6 22:46:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1458:d000] InstallationDate: Installed on 2018-05-27 (10 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ZMAX HOME 2400 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-128-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5m dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DT1800Z dmi.board.vendor: Daten Tecnologia Ltda. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 01000237030133 dmi.chassis.type: 3 dmi.chassis.vendor: ZMAX dmi.chassis.version: 01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5m:bd08/12/2014:svnZMAX:pnHOME2400:pvrTobefilledbyO.E.M.:rvnDatenTecnologiaLtda.:rnDT1800Z:rvrTobefilledbyO.E.M.:cvnZMAX:ct3:cvr01: dmi.product.name: HOME 2400 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ZMAX version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jun 6 21:36:49 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775488 Title: Ubuntu adm Firefox freezing 2 much Status in xorg package in Ubuntu: New Bug description: This make me nervous! Often the system hangs and freezes ... I do not know what I'm doing anymore. Could it be a little memory? If you can, can you give me a hand? thanks a lot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 6 22:46:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1458:d000] InstallationDate: Installed on 2018-05-27
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
I didn't see this as a bug in debhelper because, based on the Debian bug, it seems to me that the use case of one package's tmpfiles.d/ file overriding another was not considered, even if systemd can handle it underneath. From that perspective, debhelper supporting lexical sort based overriding is a feature request in debhelper, not a bug; and rsyslog packaging relying on an unimplemented debhlper "feature" is the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: New Status in systemd source package in Xenial: New Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: New Status in systemd source package in Artful: New Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d
[Touch-packages] [Bug 1771539] Re: Xorg crash
Mario Costa: 1) Please provide the output of the following terminal command (not manually attach anything found): ls -la /var/crash 2) As per your Bug Description, you are using the non-default kernel parameter: radeon.runpm=0 Could you please advise to if this is required to use? Also, if you remove it, does the crash still happen? 3) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full monitor manufacturer and model? 4) How are you connecting the monitor to the computer, via DisplayPort- to-DisplayPort cable, DisplayPort-to-HDMI cable, dongle/adapter, etc.? 5) If you keep the external monitor disconnected from the computer on boot up, and after login then plug it in does this provide a WORKAROUND? 6) Does the crash only happen after coming up from a cold boot, only after resuming from suspend, etc.? ** Changed in: xorg (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
@racb, adconrad Yes, exactly... As you can see debian bugs. In the beginning, I meant to fix it like that e.g running systemd-tmpfiles for all files in /var/lib/tmpfiles.d/ not just for systemd defined files, by running it without argument But the maintainer didn't accept mine, you can check debian discussion. I think we can fix this separately from debian? If we can, i can upload that patch. I tested it as well. and it worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: New Status in systemd source package in Xenial: New Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: New Status in systemd source package in Artful: New Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
There are multiple bugs here. I do not believe testcase of the rsyslog <-> systemd is wrong, and whilst debhelper support is good, is not what would fix rsyslog <-> systemd in Ubuntu. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Also affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in debhelper source package in Xenial: In Progress Status in rsyslog source package in Xenial: New Status in systemd source package in Xenial: New Status in debhelper source package in Artful: In Progress Status in rsyslog source package in Artful: New Status in systemd source package in Artful: New Status in debhelper source package in Bionic: In Progress Status in rsyslog source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching in theory, now only systemd is affected. but building is not affected. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See
[Touch-packages] [Bug 1356222] Re: [MIR] fcitx and related packages
Didier, please could you follow-up on the "committed tasks"? Looks like these would need some seeding. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml in Ubuntu. https://bugs.launchpad.net/bugs/1356222 Title: [MIR] fcitx and related packages Status in extra-cmake-modules package in Ubuntu: Fix Released Status in fcitx package in Ubuntu: Fix Released Status in fcitx-anthy package in Ubuntu: Fix Committed Status in fcitx-chewing package in Ubuntu: Fix Committed Status in fcitx-cloudpinyin package in Ubuntu: Fix Released Status in fcitx-configtool package in Ubuntu: Fix Released Status in fcitx-googlepinyin package in Ubuntu: Fix Committed Status in fcitx-hangul package in Ubuntu: Fix Released Status in fcitx-m17n package in Ubuntu: Fix Committed Status in fcitx-qimpanel package in Ubuntu: Fix Released Status in fcitx-qt5 package in Ubuntu: Fix Released Status in fcitx-sunpinyin package in Ubuntu: Fix Committed Status in fcitx-table-extra package in Ubuntu: Fix Committed Status in fcitx-table-other package in Ubuntu: Fix Committed Status in fcitx-unikey package in Ubuntu: Fix Released Status in libgooglepinyin package in Ubuntu: Fix Committed Status in presage package in Ubuntu: Fix Released Status in tinyxml package in Ubuntu: Fix Released Bug description: [Availability] Currently in universe [Rationale] Fcitx is a replacement candidate for IBus [Security: ] CVE entries: none Security history: none Any binaries running as root or suid/sgid ? Any daemons ? -- all running as per user session, and /usr/bin/fcitx and /usr/bin/fcitx-qimpanel will run as daemon, /usr/bin/fcitx-dbus-watcher will be pulled up when fcitx is running. Network activity: does it open any port ? Does it handle incoming network data ? -- fcitx-cloudpinyin deals with network data by using libcurl and interact with remote API from several user-choosable providers. Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? -- no, it doesn't Any source code review performed ? (The approver will do a quick and shallow check.) -- no. [Quality Assurance] Package works out of the box with no prompting. There is no reproducible major bugs in Ubuntu and Debian. Upstream is active. Package is team maintained at Debian, and is the same people working on Debian and Ubuntu. Upstream bug tracker: https://github.com/fcitx/fcitx Hardware: Does this package deal with hardware and if so how exotic is it ? -- no Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ? -- yes, some fundamental tests [UI standards] User-visible strings are internationalized using standard gettext system ? -- yes Package with translatable strings builds a PO template during package build ? -- yes End-user applications ship a desktop file? -- fcitx and fcitx-ui-qimpanel do. [Standards Compliance] FHS and Debian Policy compliant. Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ? -- package is using debhelper, [Maintenance] Desktop Team will take care of them [Dependencies] librime and brise are for fcitx-rime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extra-cmake-modules/+bug/1356222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771539] Re: Xorg crash
** Tags removed: bios-outdated-1.44 ** Tags added: latest-bios-1.44 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771539] Re: Xorg crash
Hi, thanks for you promptly response, unfortunately only now I had the time to check the things above. The HWE is the latest: ``` ~$ sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 Reading package lists... Done Building dependency tree Reading state information... Done linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62). xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1). The following packages were automatically installed and are no longer required: dkms libllvm4.0 linux-headers-4.10.0-28 linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic linux-image-extra-4.10.0-28-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. ``` The the bios is now updated, but the issue persists. ``` atritoman@atritoman-HP-EliteBook-840-G1:~$ sudo dmidecode -t 0 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x000D, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: L71 Ver. 01.44 Release Date: 04/12/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 8192 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.44 Firmware Revision: 21.89 ``` Meanwhile I had to reinstall ubuntu 16.04, its the default with Unity, same behavior. When I've started the newly reinstalled system, it seemed to work well, the dual display, after a reboot or two, it stoped working. The login screen works well and displays with dual display when I restart the laptop, but after I login it crashes, and it seems to restart the graphic environment/xserver maybe ... I can post some additional logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Touch-packages] [Bug 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: New Bug description: Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack
** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Status: New => In Progress ** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Milestone: None => ubuntu-16.04.5 ** Changed in: xorg-server-hwe-16.04 (Ubuntu Xenial) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1772632 Title: Backport packages for 16.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in llvm-toolchain-6.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: In Progress Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-intel source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.5 *** A minor update, only xserver sync, some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.83 to 2.4.91 - amdgpu: new pci-ids, bugfixes - intel: new pci-ids - drm: some new ioctl's - exynos, etnaviv, freedreno, android: fixes, new stuff llvm-toolchain-6.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-6 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for the bugfix release (bionic) is bug 1772607 [Other info] build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1772632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support
** Changed in: libdrm (Ubuntu Xenial) Milestone: None => ubuntu-16.04.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1753954 Title: Intel Whiskey Lake (WHL) graphics support Status in libdrm package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libdrm source package in Xenial: New Status in linux-oem source package in Xenial: Won't Fix Status in mesa source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: New Status in libdrm source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Status in xorg-server-hwe-16.04 source package in Bionic: Invalid Bug description: [Impact] WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, libdrm, mesa and xserver. [Test Case] Test the installation on a WHL machine, the graphical session should have full acceleration after these updates. [Regression Potential] None, just adds PCI-ID's to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1753954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775459] Re: python2.7-minimal broken in bionic beaver
you have an /usr/lib/python2.7/site-packages installed on your system. Please remove it. it's not used by anything. new installation of python2.7-minimal; /usr/lib/python2.7/site-packages is a directory which is expected a symlink to /usr/local/lib/python2.7/dist-packages. please find the package shipping files in /usr/lib/python2.7/site-packages and file a bug report to ship these in /usr/lib/python2.7/dist-packages instead ** Changed in: python2.7 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1775459 Title: python2.7-minimal broken in bionic beaver Status in python2.7 package in Ubuntu: Invalid Bug description: My high level goal is to install clang in Ubuntu 18.04 LTS Bionic Beaver, however clang's dependency package python2.7-minimal appears to be broken, at least on my machine: $ sudo apt-get install clang Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: binfmt-support clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libncurses5 libncursesw5 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev libtinfo5 llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal Suggested packages: gnustep gnustep-devel clang-6.0-doc libomp-doc llvm-6.0-doc python-doc python-tk python2.7-doc The following NEW packages will be installed: binfmt-support clang clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal The following packages will be upgraded: libncurses5 libncursesw5 libtinfo5 3 upgraded, 27 newly installed, 0 to remove and 31 not upgraded. Need to get 70.3 MB of archives. After this operation, 384 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-minimal amd64 2.7.15~rc1-1 [334 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7-minimal amd64 2.7.15~rc1-1 [1,292 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-minimal amd64 2.7.15~rc1-1 [28.1 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncurses5 amd64 6.1-1ubuntu1.18.04 [95.1 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libtinfo5 amd64 6.1-1ubuntu1.18.04 [80.3 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncursesw5 amd64 6.1-1ubuntu1.18.04 [117 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-stdlib amd64 2.7.15~rc1-1 [1,910 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7 amd64 2.7.15~rc1-1 [238 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython-stdlib amd64 2.7.15~rc1-1 [7,620 B] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1 [140 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 binfmt-support amd64 2.1.8-2 [51.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 libjsoncpp1 amd64 1.7.4-3 [73.6 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 libllvm6.0 amd64 1:6.0-1ubuntu2 [14.5 MB] Get:14 http://archive.ubuntu.com/ubuntu bionic/main amd64 libgc1c2 amd64 1:7.4.2-8ubuntu1 [81.8 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc4 amd64 8-20180414-1ubuntu2 [52.5 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc-7-dev amd64 7.3.0-16ubuntu3 [206 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc6-i386 amd64 2.27-3ubuntu1 [2,651 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32gcc1 amd64 1:8-20180414-1ubuntu2 [47.9 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32stdc++6 amd64 8-20180414-1ubuntu2 [414 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libclang-common-6.0-dev amd64 1:6.0-1ubuntu2 [3,078 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic/main amd64 libclang1-6.0 amd64 1:6.0-1ubuntu2 [7,067 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang-6.0 amd64 1:6.0-1ubuntu2 [9,292 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang amd64
[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css
Works fine here. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775447] Re: Mines counts bombs wrong on edge
** Package changed: apport (Ubuntu) => gnome-mines (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775447 Title: Mines counts bombs wrong on edge Status in gnome-mines package in Ubuntu: New Bug description: A square on the edge can count neighboring bombs incorrectly as shown in the image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1775447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775470] [NEW] totem video is unusable, video plays green screen and froze
Public bug reported: I play any video an the system become unresponsive and the playback is green. I have attached a picture from totem playing big buck bunny totally freeze and green francisco@progrest:~$ vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Ironlake Mobile - 2.1.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc francisco@progrest:~$ lspci -k 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12) Subsystem: Acer Incorporated [ALI] Core Processor DRAM Controller 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset HECI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset High Definition Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset USB2 Enhanced Host Controller Kernel driver in use: ehci-pci 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) Subsystem: Acer Incorporated [ALI] HM55 Chipset LPC Interface Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset 4 port SATA AHCI Controller Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset SMBus Controller Kernel modules: i2c_i801 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) Subsystem: Acer Incorporated [ALI] 5 Series/3400 Series Chipset Thermal Subsystem Kernel driver in use: intel ips Kernel modules: intel_ips 01:00.0 Ethernet controller: Broadcom Limited NetLink BCM57780 Gigabit Ethernet PCIe (rev 01) Subsystem: Acer Incorporated [ALI] NetLink BCM57780 Gigabit Ethernet PCIe Kernel driver in use: tg3 Kernel modules: tg3 02:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Lite-On Communications Inc AR928X Wireless Network Adapter (PCI-Express) Kernel driver in use: ath9k Kernel modules: ath9k ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QuickPath Architecture Generic Non-core Registers ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QuickPath Architecture System Address Decoder ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) Subsystem: Acer Incorporated [ALI] Core Processor QPI Link 0 ff:02.1 Host bridge: Intel Corporation 1st
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
(given architecture-all tag; replace "z hardware" with "any server hardware" - above comments are architecture independent across all Ubuntu products) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
"We understand Network Manager is good for desktop but not servers." I would not phrase it this away. On Ubuntu, Desktop defaults to NetworkManager and Server defaults to netplan Previously we defaulted to NetworkManager & ifupdown. "But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers." I would significantly challenge those statements. NetworkManager is extremely flakey, and consistently fails to reliably bring complex network configurations up, as exercised by our stress testing. It also is far from easy to use. Wrt. users restrictions, Ubuntu tries to guide users to an obviously correct, easy, default and obvious ways of doing things. However, we do indeed allow users to break their systems and keep all the broken pieces. "The reason being we going with network manager as explained is to reuse the code for all distros." I don't believe that's the right thing to do, as that does not validate how end customers will use respective distros on z hardware. All customers will most likely use whatever each distro installer sets up, and will not tear that out and go out of their way to use networkmanager in a lowest common denominator configuration (e.g. Ubuntu's network-manager is patched, and is at a different version level than other distros) "Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work." After installing a system, if you want netplan to be out of the way - and have the ability to use straight-up netwokrd/NM/etc, I'd rather recommend removing /etc/netplan/* configs and rebooting, without uninstalling netplan.io package. This would guarantee that interfaces are undeclared as managed-on-unmanaged by anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To
[Touch-packages] [Bug 1775280] Re: The second user cannot start their session, login screen has low resolution
** Tags added: login -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775280 Title: The second user cannot start their session, login screen has low resolution Status in lightdm package in Ubuntu: New Bug description: The first user can start their session successfully with autologin. When I try to switch to the second user, the login screen has very low resolution and it cannot start the secondary user session. I tried to change the value of the autologin user, than the other user session start well, but the original user session failed. That's why I think this is not a user related error, always the second user session fail, does not matter which one is the first user. The only differences between the default settings that passwordless login switch on the pam config and use nvidia-340 driver instead of noveau. The strange thing that this lightdm config works well with noveau driver, the problem with noveau driver that the video playing freeze the computer. Previously lightdm and nvidia driver work well on 16.04. This is a clean install not an upgrade from 16.04. I think the problem somewhere virtual X terminals handled by ligthDm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Jun 5 23:07:11 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
Also when I was on 17.10 beta, there was an update that broke totem (black screen instead of video). Problem appeared after the issue was fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6
[Touch-packages] [Bug 1775459] [NEW] python2.7-minimal broken in bionic beaver
Public bug reported: My high level goal is to install clang in Ubuntu 18.04 LTS Bionic Beaver, however clang's dependency package python2.7-minimal appears to be broken, at least on my machine: $ sudo apt-get install clang Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: binfmt-support clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libncurses5 libncursesw5 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev libtinfo5 llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal Suggested packages: gnustep gnustep-devel clang-6.0-doc libomp-doc llvm-6.0-doc python-doc python-tk python2.7-doc The following NEW packages will be installed: binfmt-support clang clang-6.0 lib32gcc1 lib32stdc++6 libc6-i386 libclang-common-6.0-dev libclang1-6.0 libffi-dev libgc1c2 libjsoncpp1 libllvm6.0 libobjc-7-dev libobjc4 libomp-dev libomp5 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtinfo-dev llvm-6.0 llvm-6.0-dev llvm-6.0-runtime python python-minimal python2.7 python2.7-minimal The following packages will be upgraded: libncurses5 libncursesw5 libtinfo5 3 upgraded, 27 newly installed, 0 to remove and 31 not upgraded. Need to get 70.3 MB of archives. After this operation, 384 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-minimal amd64 2.7.15~rc1-1 [334 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7-minimal amd64 2.7.15~rc1-1 [1,292 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-minimal amd64 2.7.15~rc1-1 [28.1 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncurses5 amd64 6.1-1ubuntu1.18.04 [95.1 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libtinfo5 amd64 6.1-1ubuntu1.18.04 [80.3 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libncursesw5 amd64 6.1-1ubuntu1.18.04 [117 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython2.7-stdlib amd64 2.7.15~rc1-1 [1,910 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 python2.7 amd64 2.7.15~rc1-1 [238 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython-stdlib amd64 2.7.15~rc1-1 [7,620 B] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1 [140 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 binfmt-support amd64 2.1.8-2 [51.6 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 libjsoncpp1 amd64 1.7.4-3 [73.6 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 libllvm6.0 amd64 1:6.0-1ubuntu2 [14.5 MB] Get:14 http://archive.ubuntu.com/ubuntu bionic/main amd64 libgc1c2 amd64 1:7.4.2-8ubuntu1 [81.8 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc4 amd64 8-20180414-1ubuntu2 [52.5 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 libobjc-7-dev amd64 7.3.0-16ubuntu3 [206 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main amd64 libc6-i386 amd64 2.27-3ubuntu1 [2,651 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32gcc1 amd64 1:8-20180414-1ubuntu2 [47.9 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic/main amd64 lib32stdc++6 amd64 8-20180414-1ubuntu2 [414 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic/universe amd64 libclang-common-6.0-dev amd64 1:6.0-1ubuntu2 [3,078 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic/main amd64 libclang1-6.0 amd64 1:6.0-1ubuntu2 [7,067 kB] Get:22 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang-6.0 amd64 1:6.0-1ubuntu2 [9,292 kB] Get:23 http://archive.ubuntu.com/ubuntu bionic/universe amd64 clang amd64 1:6.0-41~exp4 [3,152 B] Get:24 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libtinfo-dev amd64 6.1-1ubuntu1.18.04 [81.3 kB] Get:25 http://archive.ubuntu.com/ubuntu bionic/main amd64 llvm-6.0-runtime amd64 1:6.0-1ubuntu2 [200 kB] Get:26 http://archive.ubuntu.com/ubuntu bionic/main amd64 llvm-6.0 amd64 1:6.0-1ubuntu2 [4,838 kB] Get:27 http://archive.ubuntu.com/ubuntu bionic/main amd64 libffi-dev amd64 3.2.1-8 [156 kB]
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
So your system is obviously not an 18.04 default installation from scratch - otherwise you would have netplan.io installed and this folder and file "/etc/netplan/01-netcfg.yaml" will exist on your system. There is no known way to me to install an 18.04 system without having netplan (initially) as default. Did you have removed netplan manually from that installation? Or is your 18.04 system and upgrade from an older Ubuntu release (like 16.04 or 17.10)? If it's an 18.04 installation from scratch please provide the installation logs. They are during the installation available at /var/log/* and after the installation still available at /var/log/installer/* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
As far as I was concerned this bug was already fixed in:- 0.52.1-1ubuntu1 in the main repo, so I can't see any need for this in proposed now. But just to answer your question anyway, YES:- 0.52.2-1ubunti1-18.04.1 also fixes the issue (though now it would likely be more accurate to say it doesn't regress the earlier fix). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Committed Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9
doko tells me that this is due to people installing pip another way and pip10 doesn't include main. Perhaps we should suppress the crashes since there isn't anything we can do about it. ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775457 Title: /usr/bin/pip3:ImportError:/usr/bin/pip3@9 Status in apport package in Ubuntu: New Status in python-pip package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding python-pip. This problem was most recently seen with package version 9.0.1-2.3~ubuntu1, the problem page at https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 14:43 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767875] Re: /usr/bin/update-manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate
*** This bug is a duplicate of bug 1773316 *** https://bugs.launchpad.net/bugs/1773316 ** This bug has been marked a duplicate of bug 1773316 Object of different cache passed as argument to apt_pkg.DepCache method -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1767875 Title: /usr/bin/update- manager:ValueError:restart_icon_renderer_data_func:pkg_requires_restart:__get_candidate Status in apt package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/a2ba8d3ab5e432b3c15f172ded6d473f4c00720a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1767875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Description changed: + [Impact] + python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. + + With 1.6.1, we introduce a remapping algorithm that remaps objects of + apt.Cache() when calling apt.Cache.open(), allowing old objects to be + used after reopening, as long as they exist in the new cache. If they + don't exist in the new cache, apt_pkg.CacheMismatchError will be raised + from the apt_pkg layer. + + [Test case] + import apt + c=apt.Cache() + p=c["apt"] + c.open() + p.mark_install() + + [Regression potential] + Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than + what we have now. + + [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Changed in: update-manager (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: update-manager (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: update-manager (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Changed in: python-apt (Ubuntu Cosmic) Status: Confirmed => Fix Committed ** Changed in: python-apt (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Committed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Triaged Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Committed Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
** Summary changed: - /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install + Object of different cache passed as argument to apt_pkg.DepCache method -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: /usr/bin/update-manager:ValueError:foreach_cb:packages_are_selected:is_selected:marked_install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in python-apt source package in Bionic: Confirmed Status in update-manager source package in Bionic: Confirmed Status in python-apt source package in Cosmic: Confirmed Status in update-manager source package in Cosmic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775442] Re: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9
** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1775442 Title: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9 Status in systemd package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709603] Re: apt {upgrade, install, source} require an update call first
Just a comment...
'apt' indicates that its cli is unstable and should not be relied upon by
scripts.
So fixing this general problem in 'apt' (and not apt-get) means you fix it
possibly for humans who are typing things, but all non-human package
installations needlessly have to 'apt-get update'. :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1709603
Title:
apt {upgrade,install, source} require an update call first
Status in apt package in Ubuntu:
Confirmed
Bug description:
I think that this should be tracked in its own separate bug tracking
my specific UX objection to the current status quo.
See
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5,
subsequent discussion and
https://twitter.com/chr1sa/status/894048628284604416
We think that the updating of indexes should be an implementation
detail of "apt upgrade" and "apt install", rather than something
exposed to the user. If updating is judged be required (for example
the index is more than X old), then it should be done automatically
before the requested operation commences.
Here's one proposed implementation:
1) Fix bug 1429285 ("apt-get update --if-necessary").
2) Add an option to have "apt install" and "apt upgrade" (also "apt
full-upgrade", etc?) automatically and internally call the
implementation of "apt-get update --if-necessary" first.
3) Enable the option by default on Ubuntu.
This would change the behaviour of "apt", which AIUI is intended to be
the user focused CLI. It wouldn't change the behaviour of "apt-get",
which AIUI needs to retain behavioural backwards compatibility for
existing scripts.
Then we could promote "apt install" and "apt upgrade" as much simpler
commands to operate.
Note that Julian disagreed with this proposed behaviour change in
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7.
I think that the very user-focused Ubuntu perspective should be to
focus on the common use case for "apt". Hence my (compromise)
suggestion that we implement this as an option upstream, and then
leave it to distros to choose the default behaviour for their users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)
I've checked iowait using iotop during lags and revealed no spikes or something like that. So it's not a performance problem at all. I believe gstreamer is just dropping frames due to some bugs. I had 17.10 installed and had no issue that time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1774915 Title: Video freezes and stutters when using totem (audio continues fine) Status in gnome-shell package in Ubuntu: Incomplete Status in gstreamer1.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Advised to file a bug report after posting on "Call for testing: Video playback in 18.04". Running 18.04 LTS as fresh install (not upgraded from previous version - older version still installed in separate partition). Xorg session. System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor, integrated Intel video Playing any local video file (regardless of video format - flv, mp4, avi), the video will randomly lag in playback. Audio is not affected, it plays back correctly. Very occasional lags in browsers (Firefox and Chrome) on pages with a lot of active graphics (flash or HTML5). Browser lags significantly improved after installing synaptic driver for touchpad operation (I have no idea why this would affect video playback - I simply note that it happened). I can pick a random video on YouTube and watch it in Firefox or Chrome without lag (even full-screen). However, if I grab a local copy of the video (using, for instance, Clipgrab) and play it using Totem, I get lag. I was also advised to try using mpv - I still get lag in mpv, although not as pronounced. tracy@tracy-hp:~$ sudo apt-cache policy totem [sudo] password for tracy: totem: Installed: 3.26.0-0ubuntu6 Candidate: 3.26.0-0ubuntu6 Version table: *** 3.26.0-0ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I was also asked to include output of lspci -k - shown below: tracy@tracy-hp:~$ lspci -k 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family DRAM Controller 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) Kernel driver in use: pcieport Kernel modules: shpchp 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family MEI Controller Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family USB Enhanced Host Controller Kernel driver in use: ehci-pci 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 05) Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC Controller Kernel driver in use: lpc_ich Kernel
[Touch-packages] [Bug 1775452] [NEW] Nvidia problems
Public bug reported: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E5M/300E5L ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RED.019.171215.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP300E5M-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9046A07-C01-G001-S0001+10.0.15063 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RED.019.171215.ZW:bd12/15/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E5M/300E5L:pvrP06RED:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5M-XD1BR:rvrSGL9046A07-C01-G001-S0001+10.0.15063:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 300E5M/300E5L dmi.product.version: P06RED dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775452 Title: Nvidia problems Status in xorg package in Ubuntu: New Bug description: I have installed the nvidia driver 390 but when I rollback to nouveau my kern.log e syslog flood with error until have space in my hard drive. My computer doesn't hibernate or sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 6 15:42:57 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.59, 4.15.0-20-generic, x86_64: installed nvidia, 390.59, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c784] Subsystem: Samsung Electronics Co Ltd GM108M [GeForce 920MX] [144d:c784] InstallationDate: Installed on 2018-05-05 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 2232:1080 Silicon Motion Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Touch-packages] [Bug 1763844] Re: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1763844 Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in python-apt package in Ubuntu: Incomplete Bug description: Problem occurred setting the displays arrangement ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.0~rc2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 17:34:14 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-04-13 (364 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: python-apt Title: package python3-apt 1.6.0~rc2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1763844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770327] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1770327 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: I couldn't access ubuntu desktop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed May 9 11:52:20 2018 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2018-02-27 (71 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1770327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763822] Re: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1763822 Title: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in software-properties package in Ubuntu: Incomplete Bug description: Package crash after log in ProblemType: Package DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.28 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 17:34:14 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-04-13 (364 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: software-properties Title: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775447] [NEW] Mines counts bombs wrong on edge
Public bug reported: A square on the edge can count neighboring bombs incorrectly as shown in the image. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "error example" https://bugs.launchpad.net/bugs/1775447/+attachment/5149441/+files/mines%20bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775447 Title: Mines counts bombs wrong on edge Status in apport package in Ubuntu: New Bug description: A square on the edge can count neighboring bombs incorrectly as shown in the image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775441] Re: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen
** Package changed: lightdm (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775441 Title: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen Status in gdm3 package in Ubuntu: New Bug description: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767982] Re: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Does this actually have anything to do with util-linux? What makes dpkg give this error message? ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1767982 Title: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: Incomplete Bug description: Since my last update, i'm getting this error every time when i want to install something. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libmount1:i386 2.31.1-0.4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Apr 30 11:29:35 2018 DpkgTerminalLog: dpkg: error processing package libmount1:i386 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-17 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: util-linux Title: package libmount1:i386 2.31.1-0.4ubuntu3 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1767982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774573] Re: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags added: pyclean-not-found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774573 Title: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in apport package in Ubuntu: New Bug description: The computer prompted me an error when I start it today. I don't know what else happened. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: python3-apport:amd64: Install apport:amd64: Install NULL: ConfigurePending Architecture: amd64 CrashReports: 600:0:119:103009:2018-06-01 00:27:18.217459917 -0400:2018-06-01 00:27:19.217459917 -0400:/var/crash/apport.0.crash Date: Fri Jun 1 00:27:19 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2018-04-03 (59 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: apport Title: package apport 2.20.7-0ubuntu3.7 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
To anyone doing something about this bug, it could also be fixed by actually using the selection from the Select Audio Device dialogue and, you know, remembering it and using it. This would improve things for everyone much more than just making this singular Dell hardware problem go away. Nobody should have to use that dialogue every time they plug in the same device. Bad user experience, bad design. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775441] [NEW] 18.04 crashed on startup, hanging at purple login screen handoff to normal screen
Public bug reported: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1775441 Title: 18.04 crashed on startup, hanging at purple login screen handoff to normal screen Status in lightdm package in Ubuntu: New Bug description: Insanely, the boot before, and the boot after, were perfectly smooth and successful, and stayed on for hours. This single startup required a force restart after hanging on the purple that comes after typing password and hitting enter on login, and just before normal gnome desktop appears. I'm not sure it's lightdm, but I read that lightdm still runs the login screen, and was responsible for previous problems at this stage in the bootup process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 12:50:56 2018 InstallationDate: Installed on 2018-04-26 (41 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775442] [NEW] systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1775442 Title: systemd 237-3ubuntu10 ADT test failure with linux-gcp 4.15.0-1009.9 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
Hello Mark-pcnetspec, or anyone else affected, Accepted vte2.91 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vte2.91/0.52.2-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vte2.91 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Committed Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
So apport needs to catch the exception and do nothing / not register an excepthook on unsupported python versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
python 3.7 is not a supported version, hence modules are not built for it. ** Changed in: python-apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in apport package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
Since the ticket was opened against 18.04, and since 18.04 installations come with and use netplan by default with again networkd as the default renderer (and not NetworkManager), NetworkManager just cannot work by default. If you want to work with NetworkManager on an 18.04 installation that's using netplan, the described re-configuration is needed and the renderer needs to be changed from networkd to NetworkManager - that's not a bug, that's intended and caused by the introduction of netplan (since about 17.10). With that change NetworkManager should be able to manage qdio devices (see end of comment #3 - devices are listed as managed). If you still have problems managing the devices _after_ doing the re- config there might be a bug, but I don't see that right now (but I for sure didn't covered your entire use case that I just don't know). We understand that behavior is now a bit different compared to other distributions. There were some bugs in the past on NetworkManager and netplan on previous Ubuntu releases, like the one mentioned by you in the bug description: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 which is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547 and already 'Fix Release' (since quite some time). And btw. comment 26: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/comments/26 confirms that the above renderer change works. If issues still occur on other Ubuntu releases (not 18.04, but for example 16.04) that are not yet addressed in an LP bug, please open a separate bug on them. And if there are still issues managing qdio devices after the change above, we may address them is a separate ticket, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to:
[Touch-packages] [Bug 1775429] [NEW] Label in stackswitcher button is not bold when selected
Public bug reported: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775429 Title: Label in stackswitcher button is not bold when selected Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1775429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775432] [NEW] Stackswitcher buttons in gnome-software are not themed alike
Public bug reported: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in ubuntu-themes package in Ubuntu: New Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1775432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775426] [NEW] [MPOW, playback] fails after a while
Public bug reported: Since upgrade from xenial to bionic I'm having problems with sound via bluetooth, which is reproduced with a lot of glitches and very chocked. My bluetooth is integrated in the laptop motherboard and I'm using an mpow bluetooth headphone. As I said, whith the same laptop and headphone but xenial worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amateo 2330 F pulseaudio /dev/snd/controlC1: amateo 2330 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:17:37 2018 InstallationDate: Installed on 2018-05-14 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: MPOW Symptom_PulseAudioLog: jun 06 17:35:29 amateo-EXCALIBUR dbus-daemon[1010]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=120 pid=1314 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MPOW, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EXCALIBUR dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pnEXCALIBUR:pvr1.0:rvnSLIMBOOK:rnEXCALIBUR:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: EXCALIBUR dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1775426 Title: [MPOW, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Since upgrade from xenial to bionic I'm having problems with sound via bluetooth, which is reproduced with a lot of glitches and very chocked. My bluetooth is integrated in the laptop motherboard and I'm using an mpow bluetooth headphone. As I said, whith the same laptop and headphone but xenial worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amateo 2330 F pulseaudio /dev/snd/controlC1: amateo 2330 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:17:37 2018 InstallationDate: Installed on 2018-05-14 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: MPOW Symptom_PulseAudioLog: jun 06 17:35:29 amateo-EXCALIBUR dbus-daemon[1010]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=120 pid=1314 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MPOW, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EXCALIBUR dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pnEXCALIBUR:pvr1.0:rvnSLIMBOOK:rnEXCALIBUR:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: EXCALIBUR dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1775426/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 I think it is wrong that you won't tell me what's wrong with MY computer just because someone with wheel bits set found the problem first. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1765285 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: Confirmed Bug description: ??? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 06:46:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-21 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) Lsusb: Bus 002 Device 002: ID 0781:5591 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759961] Re: Update to bluez 5.50
** Summary changed: - Update to bluez 5.50 (mostly bug-fix release) + Update to bluez 5.50 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765285] Re: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex()
*** This bug is a duplicate of bug 1754214 *** https://bugs.launchpad.net/bugs/1754214 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1765285 Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() Status in systemd package in Ubuntu: Confirmed Bug description: ??? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 06:46:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-21 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) Lsusb: Bus 002 Device 002: ID 0781:5591 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-17-generic root=UUID=624ad287-69d9-4615-a6a0-b840f3ff8c6d ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __GI___pthread_timedjoin_ex (threadid=139717271447296, thread_return=0x0, abstime=0x0, block=) at pthread_join_common.c:89 ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in __GI___pthread_timedjoin_ex() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765923] Re: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug?
I had this issue and resolved it by modifying the 10-nvidia.conf file to add the line: Option "PrimaryGPU" "true" The problem that I had was that the system would boot with the Intel GPU and once it go to the X-Display it attempted to use the NVidia drivers which were not properly initialized. ** Attachment added: "10-nvidia.conf" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+attachment/5149387/+files/10-nvidia.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1765923 Title: Nvidia driver leads to black screen on bionic 18.04 SDDM LightDM bug? Status in apt package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Using the April 19th daily build of Kubuntu 18.04 I installed the Nvidia drivers via the following command. sudo ubuntu-drivers autoinstall The install process proceeds fine and after a logout process I get a black screen. I tried this on the April 17th daily build of bionic and a reboot also results in a black screen. The following is a question which was submitted by a Ubuntu 17.10 user: QUOTE After I installed latest Nvidia driver-390 and tried to boot after shutting down once I faced a black screen problem. since, I'm a noob but something related to nvidia drivers couldn't be started. Then I followed https://askubuntu.com/a/968692/802490 While following these instructions re-installing of nvidia drivers failed. The only things that worked is purging the drivers and changing "WaylandEnable=false" in (/etc/gdm3/custom.conf). Now, I want to re-install nvidia drivers again but I'm afraid that this will lead to that problem again. Can anyone help in re-installing the driver such that I won't face that problem? END QUOTE THE WORK AROUND Use Ctrl-Alt-f6 to get to a login prompt. Login run "startx" The x server will start and Nvidia drivers will function. THE PROBLEM When I try to run SDDM I get an error (Which I will try to copy down to add to this bug when I am on a different computer than the one I am reporting the bug about.). Installing lightDM does not work... it installs but is either will not run or will not actually start a x session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1765923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769400] Re: suspend no longer functions after update to 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pm-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1769400 Title: suspend no longer functions after update to 18.04 Status in pm-utils package in Ubuntu: Confirmed Bug description: Suspend does not complete. The system stops in an unknown state without fully suspending and without ability to wake. Problem began on upgrade to Ubuntu 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pm-utils 1.4.1-17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat May 5 13:31:03 2018 InstallationDate: Installed on 2015-03-25 (1137 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1769400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf
> I see the second PackageKit pull request has not yet been approved by upstream - could we get someone reviewing it and merging before we proceed? I think the SRU remains blocked on this question? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Please test proposed package
Hello Nikkus, or anyone else affected, Accepted menu into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Hello Nikkus, or anyone else affected, Accepted menu into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu1.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: menu (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: menu (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Please test proposed package
Hello Nikkus, or anyone else affected, Accepted menu into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/menu/2.1.47ubuntu1.17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: menu (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: New Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: New Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771102] Re: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache
Does anyone know of anything I can do to move forward? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1771102 Title: 17.10->18.04 LTS hangs, CPU stalls in apt-pkg cache Status in python-apt package in Ubuntu: New Bug description: When I do as root: do-release-upgrade The bionic tarball is downloaded and the python based "bionic" process is forked. On the screen I see the first "Reading cache..." message and then the process spikes the CPU to 100% where it stays there forever (I waited 15-20 minutes and there was no change in CPU state). Here is the dist-upgrade log file: 2018-05-14 07:17:19,308 INFO uname information: 'Linux kitt 4.13.0-41-generic #46-Ubuntu SMP Wed May 2 13:38:30 UTC 2018 x86_64' 2018-05-14 07:17:19,594 INFO apt version: '1.5.1' 2018-05-14 07:17:19,594 INFO python version: '3.6.3 (default, Oct 3 2017, 21:45:48) [GCC 7.2.0]' 2018-05-14 07:17:19,596 INFO release-upgrader version '18.04.17' started 2018-05-14 07:17:19,600 INFO locale: 'en_US' 'UTF-8' 2018-05-14 07:17:19,605 INFO screen could not be run 2018-05-14 07:17:19,744 DEBUG Using 'DistUpgradeViewText' view 2018-05-14 07:17:19,788 DEBUG enable dpkg --force-overwrite 2018-05-14 07:17:19,817 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' strace output of the "bionic" process: $ sudo strace -f -p 6469 strace: Process 6469 attached with 3 threads [pid 6546] restart_syscall(<... resuming interrupted poll ...> [pid 6547] restart_syscall(<... resuming interrupted poll ...>strace: [ Process PID=6469 runs in x32 mode. ] top output: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6469 root 20 0 270048 33108 15728 R 99.7 0.1 0:38.85 bionic 6555 pisymbol 20 0 46736 4376 3344 R 0.7 0.0 0:00.04 top Looking at this further, it seems that the installer sets the the "rootdir=/" when it initiates the python-apt's Cache class. This hangs. I can reproduce this by simply changing it's test code to pass rootdir="/" and it hangs. It sorta smells like a deadlock issue though deep in the C++ module (apt_pkg) that backs the python one (GetLock?). But I'm not 100% sure. This behavior is seen on my 32-core Threadripper machine (AMD64). This is 17.10 latest with: $ dpkg -l python-apt libapt-pkg5.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii libapt-pkg5.0:amd641.5.1 amd64package management runtime library ii python-apt 1.4.0~beta3build2 amd64Python interface to libapt-pkg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1771102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release
** Changed in: libglvnd (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1772607 Title: Mesa 18.0.5 stable release Status in libglvnd package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libglvnd source package in Bionic: In Progress Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point release of the series. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1772607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Changed in: menu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in menu source package in Xenial: In Progress Status in apt source package in Artful: New Status in menu source package in Artful: New Status in apt source package in Bionic: New Status in menu source package in Bionic: New Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775392] [NEW] at-spi-bus-launcher makes Xorg crash when resuming from suspend
Public bug reported: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Tags: crash sigbus xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: New Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
In /usr/share/themes/Radiance/gtk-3.20/apps create the link
sudo ln -s gedit.css gnome-builder.css
I did not see any difference in gedit, but the error message disappears.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
New
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775380] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1775380 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1775380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775380] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1775380 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) all time that I try to update or remove or install something receive error like above ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 6 13:19:37 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1775380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688575] Update Released
The verification of the Stable Release Update for openldap has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s
[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
This bug was fixed in the package openldap - 2.4.42+dfsg-2ubuntu3.3 --- openldap (2.4.42+dfsg-2ubuntu3.3) xenial; urgency=medium [ Ryan Tandy ] * d/p/ITS-8648-check-result-of-ldap_int_initialize-in-ldap.patch, d/p/ITS-8648-init-SASL-library-in-global-init.patch: Import upstream patches to fix memory corruption caused by calling sasl_client_init() multiple times and possibly concurrently. (ITS#8648) (LP: #1688575) -- Andreas Hasenack Tue, 22 May 2018 10:54:12 -0300 ** Changed in: openldap (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Bug description: [Impact] Concurrent SASL authentications could trigger a segfault. This was observed by the bug reporter during replication from a master to a slave, and can be reproduced with a test program. The fix is applied upstream, see comment #13. [Test Case] * Create a fresh xenial VM or container and login. Update the apt repositories: sudo apt update * Create a local directory and cd into it: mkdir test && cd test * Download the test attachments from this bug: Makefile, sasltest.c and testscript: wget https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript * Build with $ apt install libsasl2-dev libldap2-dev $ make * Execute the testscript with sudo once. It shall fail at the very end with a core dump: sudo sh ./testscript (...) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Export this var: export LDAPSASL_SECPROPS=none * Run the actual test script a few more times to confirm the crasH: $ ./sasltest rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. rc = -6 (Unknown authentication method) sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed. Aborted (core dumped) * Install the updated packages from proposed * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported: $ echo $LDAPSASL_SECPROPS none $ ./sasltest $ This time the test completes without crashing. [Regression Potential] This is SASL authentication, and with kerberos nonetheless (in the case of the bug reporter). I suspect not many people deploy this due to its complexity. The ones that have such a setup, however, tend to know what they are doing, so if they say the problem is fixed for them, I believe it is. About this particular change, it's committed upstream and also in debian, and @rtandy was kind enough to provide a sample test script that exhibits the problem. [Other Info] Since the fix is applied upstream and in Debian, there shouldn't be additional surprises here. [Original description] I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP
[Touch-packages] [Bug 1775369] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Occured while dist upgrade 14.04 lts to 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.12 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 6 09:40:01 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-02-17 (840 days ago) InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-12-01 (186 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775369 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in openssl package in Ubuntu: New Bug description: Occured while dist upgrade 14.04 lts to 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.12 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 6 09:40:01 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-02-17 (840 days ago) InstallationMedia: Ubuntu-GNOME 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-12-01 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1775369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775018] Comment bridged from LTC Bugzilla
--- Comment From patrick.ste...@de.ibm.com 2018-06-06 05:16 EDT--- > Is this upstreamed already? What is the upstream commit id? As i said in #1, openssl upstream/master and 1.1.0 backports are not affected. The bug was introduced with the 1.0.2 backport (of upstream commit 96530eea93d27e536f4e93956256cf8dcda7d469). > An explanation of the effects of the bug on users Using openssl tls 1.2 with aes-gcm cipher-suites on s390 can lead to unexpected authentication failures. > justification for backporting the fix to the stable release Fix unexpected authentication failures when using openssl tls 1.2 with aes-gcm cipher-suites on s390. > In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug After openssl 1.0.2 most data structures were made opaque. Backporting to 1.0.2 means reversing this process. In case of this backport, accidentially the wrong structure member was assessed in one place in the s390 platform-specific aes-gcm tls code path. The uploaded fixes this bug by accessing the right structure member. > detailed instructions how to reproduce the bug > these should allow someone who is not familiar with the affected package to > reproduce the bug and verify that the updated package fixes the problem. Apply original backport patches to openssl 1.0.2 source. Build and run the test suite (make test). Observe test case failure when testing aes- gcm cipher suites. Apply the uploaded fix and repeat. Observe the test suite pass. > [Regression Potential] ... I dont see any risk for regression regarding this fix. > Specifically how to test/excercise this code path? As noted above, the openssl test suite exercises this code path (at least with high probability i.e., i hit the problem at 5/5 runs). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
