[Touch-packages] [Bug 2047926] Re: vim Matchit's parentheses matching function breaks in tex files
** Summary changed:
- matchit vim matching parentheses tex files
+ vim Matchit's parentheses matching function breaks in tex files
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2047926
Title:
vim Matchit's parentheses matching function breaks in tex files
Status in vim package in Ubuntu:
New
Bug description:
** lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
**apt-cache policy vim
vim:
Installed: 2:8.2.3995-1ubuntu2.15
Candidate: 2:8.2.3995-1ubuntu2.15
Version table:
*** 2:8.2.3995-1ubuntu2.15 500
500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
2:8.2.3995-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
**The functionality of the package 'Matchit' that is shipped with vim 8.2 is
broken for .tex files.
**Minimal example:
The file test.tex contains the following text:
(hello)
**Expected behavior: when the cursor is placed on the '(' character, a
keyboard press of the '%' button should take the cursor to the ')' character.
**Faulty behavior: instead, an error message pops up, saying:
Error detected while processing function
matchit#Match_wrapper[161]..65_Par
seSkip:
line 10:
E488: Trailing characters: . strpart(skip,2). "'"
Error detected while processing function matchit#Match_wrapper:
line 174:
E121: Undefined variable: r
line 176:
E121: Undefined variable: r
**Possible solution: replace the file
/usr/share/vim/vim82/pack/dist/opt/matchit/autoload/matchit.vim with
the newest version of matchit.vim (commit 9c1c78e,
https://github.com/chrisbra/matchit/blob/master/autoload/matchit.vim)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: vim 2:8.2.3995-1ubuntu2.15
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 3 11:53:45 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
InstallationDate: Installed on 2020-03-16 (1388 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
SourcePackage: vim
UpgradeStatus: Upgraded to jammy on 2023-12-10 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047926/+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 2047926] [NEW] matchit vim matching parentheses tex files
Public bug reported:
** lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
**apt-cache policy vim
vim:
Installed: 2:8.2.3995-1ubuntu2.15
Candidate: 2:8.2.3995-1ubuntu2.15
Version table:
*** 2:8.2.3995-1ubuntu2.15 500
500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
2:8.2.3995-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
**The functionality of the package 'Matchit' that is shipped with vim 8.2 is
broken for .tex files.
**Minimal example:
The file test.tex contains the following text:
(hello)
**Expected behavior: when the cursor is placed on the '(' character, a keyboard
press of the '%' button should take the cursor to the ')' character.
**Faulty behavior: instead, an error message pops up, saying:
Error detected while processing function matchit#Match_wrapper[161]..65_Par
seSkip:
line 10:
E488: Trailing characters: . strpart(skip,2). "'"
Error detected while processing function matchit#Match_wrapper:
line 174:
E121: Undefined variable: r
line 176:
E121: Undefined variable: r
**Possible solution: replace the file
/usr/share/vim/vim82/pack/dist/opt/matchit/autoload/matchit.vim with the
newest version of matchit.vim (commit 9c1c78e,
https://github.com/chrisbra/matchit/blob/master/autoload/matchit.vim)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: vim 2:8.2.3995-1ubuntu2.15
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 3 11:53:45 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
InstallationDate: Installed on 2020-03-16 (1388 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
SourcePackage: vim
UpgradeStatus: Upgraded to jammy on 2023-12-10 (23 days ago)
** Affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2047926
Title:
matchit vim matching parentheses tex files
Status in vim package in Ubuntu:
New
Bug description:
** lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
**apt-cache policy vim
vim:
Installed: 2:8.2.3995-1ubuntu2.15
Candidate: 2:8.2.3995-1ubuntu2.15
Version table:
*** 2:8.2.3995-1ubuntu2.15 500
500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
2:8.2.3995-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
**The functionality of the package 'Matchit' that is shipped with vim 8.2 is
broken for .tex files.
**Minimal example:
The file test.tex contains the following text:
(hello)
**Expected behavior: when the cursor is placed on the '(' character, a
keyboard press of the '%' button should take the cursor to the ')' character.
**Faulty behavior: instead, an error message pops up, saying:
Error detected while processing function
matchit#Match_wrapper[161]..65_Par
seSkip:
line 10:
E488: Trailing characters: . strpart(skip,2). "'"
Error detected while processing function matchit#Match_wrapper:
line 174:
E121: Undefined variable: r
line 176:
E121: Undefined variable: r
**Possible solution: replace the file
/usr/share/vim/vim82/pack/dist/opt/matchit/autoload/matchit.vim with
the newest version of matchit.vim (commit 9c1c78e,
https://github.com/chrisbra/matchit/blob/master/autoload/matchit.vim)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: vim 2:8.2.3995-1ubuntu2.15
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 3 11:53:45 2024
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
InstallationDate: Installed on 2020-03-16 (1388 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
SourcePackage: vim
UpgradeStatus: Upgraded to jammy on 2023-12-10 (23 day
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Follow-up to #34, on a system where unattended-upgrades happens to be
running when shutdown is called, the shutdown does not wait, therefore
any running dpkg is killed and the package left in an inconsistent
state.
- Xenial with single partition, InstallOnShutdown not defined.
This may be a separate issue, but I'll investigate further before
raising it as such.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Xenial:
Triaged
Status in unattended-upgrades source package in Yakkety:
Triaged
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
The Unit file in #33 works for me, ie stops the 10 minute hang, when
unattended-upgrades is not running.
- Xenial with /var as a separate FS, InstallOnShutdown="false"
I will try to create a test case where unattended-upgrades is running
when shutdown is called.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Xenial:
Triaged
Status in unattended-upgrades source package in Yakkety:
Triaged
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1554848] Re: Please randomise automatic updates over a longer period
My apologies - this delay is already configurable using APT::Periodic::RandomSleep ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Load on the main Ubuntu archive servers is rather peakish, and tends to create a traffic peak on our Internet links at fairly regular times each day, preventing customers from accessing the archive. This impacts the cloud archive mirrors using the ubuntu-repository-cache charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently-announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+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 1554848] Re: Please randomise automatic updates over a longer period
It would be good to have the delay length as a configuration option, I would like to reduce the random delay for some of my PCs which are not turned on very often. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Load on the main Ubuntu archive servers is rather peakish, and tends to create a traffic peak on our Internet links at fairly regular times each day, preventing customers from accessing the archive. This impacts the cloud archive mirrors using the ubuntu-repository-cache charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently-announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+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 1494225] Re: Call audio is not routed to headset with HFP
sorry not been able to set my phone up for logging at the moment - although reasonably technical and used to using the cli for out of the normal occasions, I don't go for the cli normally and prefer a gui, so just need to get my head around setting up. Not sure if it helps, but I did notice though that for normal operation as long as you are slow in connecting everything then it does all seem to hang together. Here's what I do (to get it to work); - have bluetooth switched on on the phone (with the pairing already completed) - switch on the headset and wait for the bluetooth icon to go from a black background, to white and then back to black. - wait 20-30 seconds (till I think it will have sorted itself out) - press the button on the headset (the one that initiates a connection and is also used for answering and ending calls) - wait till the bluetooth icon goes white and the bluetooth volume 'overlay' is shown - this can take 30-40 seconds I can now make or receive calls and the sound/mic are passed to/from the headset correctly. If I try to 'rush' this cycle or answer a call then switch on the headset, that's when the problem shows and I get connection to the headset to no sound to or from the headset or speakers/phone mic. -- 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/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+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 1494225] Re: Call audio is not routed to headset with HFP
Think this affects me too on my MX4 using HTC BH M200 headset. If there's anything I can send from the phone that'll help, let me know. Looks by the packages that are affected that it could also be loosely related to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1544477 This started with me with OTA-9 and continues after OTA-9.1 -- 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/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
I did change the sounds from the default to positive the other week as I thought I was missing text messages due to not hearing them - then I did the tests and found it was due to only the vibration working - before it was left on the Amsterdam default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
here's a zip of the media hub files before and after it going wrong (I'm assuming that this is what the .gz files are). I don't recall changing the volume or silent status until after it went wrong yesterday apart from on Friday evening when it was on silent for around 1-2 hours. Media-hub-7.gz should show when it was in silent mode (Friday evening). Hope this info is useful - if not and you need something else please holla. ** Attachment added: "mx4 media hub.zip" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4578374/+files/mx4%20media%20hub.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
I believe that it is inconsistent (more than just putting into silent and back out). I had my MX4 in silent on Friday evening then back to normal Saturday seemed OK Sunday morning I thought the SMS sound notification wasn't working (vibration still good) - I had to hard reset my phone 2-3 times to get bluetooth working again to my headset and phone app crashed as locked up the screen (bluetooth kept connecting but no voice transferred, then after 2-3 hard resets (power button for 10 secs) all came good again). Sunday evening SMS notifications all ok for multiple texts from multiple people, sent various SMS's and a single MMS, again OK received SMS after this, sound still good Something happened (unknown what though) now sound failed again on SMS... Would you like a copy of the ubuntu-phablet-stream-volumes.tdb file again or anything else I can provide to assist? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1486456] Re: Please set back libvpx1 into Wily archive
That does fix it, wily wasn't an option before On Nov 25, 2015 2:35 PM, "Marcos William Ferretti" wrote: > sudo sed -i 's/vivid/wily/' /etc/apt/sources.list > sudo apt-get update > sudo apt-get install virtualbox-5.0 > > from: > > https://askubuntu.com/questions/696870/dependency-errors-when-trying-to-install-virtualbox-5-0-on-15-10 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1486456 > > Title: > Please set back libvpx1 into Wily archive > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1486456 Title: Please set back libvpx1 into Wily archive Status in libvpx package in Ubuntu: Confirmed Bug description: Wanting to install virtualbox 5.0 from virtualbox.org, as the wily archive one (5.02-dfsg-2) has a vboxpci iommu issue. but i require libvpx1 to install (and no more available into Wily archive) https://launchpad.net/ubuntu/+source/libvpx virtualbox-5.0: Depends: libvpx1 (>=1.0.0) but it is not installable Error with the Wily package: dmesg | grep -i iommu [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on [0.00] DMAR: IOMMU enabled [ 32.662814] vboxpci: IOMMU not found (not registered) (this is a test with intel_iommu=on kernel parameter, but without i get the same result. So i need the version from virtualbox.org) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+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 1486456] Re: Please set back libvpx1 into Wily archive
I did a work around, I went and downloaded the older version at http://packages.ubuntu.com/trusty/libvpx1 and installed it with dpkg. This seemed to make everything happy for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1486456 Title: Please set back libvpx1 into Wily archive Status in libvpx package in Ubuntu: Confirmed Bug description: Wanting to install virtualbox 5.0 from virtualbox.org, as the wily archive one (5.02-dfsg-2) has a vboxpci iommu issue. but i require libvpx1 to install (and no more available into Wily archive) https://launchpad.net/ubuntu/+source/libvpx virtualbox-5.0: Depends: libvpx1 (>=1.0.0) but it is not installable Error with the Wily package: dmesg | grep -i iommu [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on [0.00] DMAR: IOMMU enabled [ 32.662814] vboxpci: IOMMU not found (not registered) (this is a test with intel_iommu=on kernel parameter, but without i get the same result. So i need the version from virtualbox.org) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+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 1512066] Re: Desktop screen and icon corruption
If I may take the opportunity to show examples of corruption taken as screenshots prior to reverting to 15.04. At present I am trialing mint as a second resort. I will attempt the recommendations. Like hundreds if not thousands who dislike windows in any format, I changed to Ubuntu 10.4 many years ago, and progressed through upgrades as they became available. It is only since moving from 14.10 that these corruptions began. Best Regards. and thank you for the response Geoff On 7 November 2015 at 14:11, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Geoff, thank you for reporting this and helping make Ubuntu better. > > As per > > http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3785043&swLangOid=8&swEnvOid=4060 > an update to your computer's buggy and outdated BIOS is available > (1.26). If you update to this following > https://help.ubuntu.com/community/BIOSUpdate does it change anything? > > If it doesn't, could you please both specify what happened, and provide > the output of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. As well, you don't > have to create a new bug report. > > Once the BIOS is updated, if the problem is still reproducible, and the > information above is provided, then please mark this report Status New. > Otherwise, please mark this as Invalid. > > Thank you for your understanding. > > ** Tags added: bios-outdated-1.32 > > ** Tags removed: bios-outdated-1.32 > ** Tags added: bios-outdated-1.26 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1512066 > > Title: > Desktop screen and icon corruption > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > This is now the 3 rd time to reinstall 15.10. Previously the 15.04 > version has been re-installed. > Under 15.04 the problem (bug) was restricted to the desktop background > image in that after a few days and new updates loaded the screen became > corrupted with the appearance of a view like looking through opaque reed > glass. The blame was put on 'Variety' which was in use. Peter Levi terms > this problem a 'low key bug'? It makes no difference whether 'Variety' is > in use or not > As the problem (bug) only affected the desktop background then it was > workable. > The new release of 15.10 was hoped to iron out the problem, but once > again after receiving updates corruption began, and is much more severe in > that icons become distorted when the mouse passes over them sections of > text work become a. invisible or b. distorted to be unreadable. > To date I have re-installed 15.10 four times. Everything is stable until > I begin to accept updates. and the corruption begins. > I have brought up this problem before since 23 rd October. > I cannot be the only individual suffering from this problem. I have two > machines and the results are the same on both. I have changed monitors to > no avail. > The programme was re-installed yesterday and is stable without any > updates. > I run also windows 10 on this machine but have experienced no problems > with display or documents text/ icons > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: xorg 1:7.7+7ubuntu4 > ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 > Uname: Linux 3.19.0-15-generic x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.17.2-0ubuntu1 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Sun Nov 1 08:34:28 2015 > DistUpgraded: Fresh install > DistroCodename: vivid > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Device [103c:3034] > Subsystem: Hewlett-Packard Company Device [103c:3034] > InstallationDat
[Touch-packages] [Bug 1512066] [NEW] Desktop screen and icon corruption
Public bug reported: This is now the 3 rd time to reinstall 15.10. Previously the 15.04 version has been re-installed. Under 15.04 the problem (bug) was restricted to the desktop background image in that after a few days and new updates loaded the screen became corrupted with the appearance of a view like looking through opaque reed glass. The blame was put on 'Variety' which was in use. Peter Levi terms this problem a 'low key bug'? It makes no difference whether 'Variety' is in use or not As the problem (bug) only affected the desktop background then it was workable. The new release of 15.10 was hoped to iron out the problem, but once again after receiving updates corruption began, and is much more severe in that icons become distorted when the mouse passes over them sections of text work become a. invisible or b. distorted to be unreadable. To date I have re-installed 15.10 four times. Everything is stable until I begin to accept updates. and the corruption begins. I have brought up this problem before since 23 rd October. I cannot be the only individual suffering from this problem. I have two machines and the results are the same on both. I have changed monitors to no avail. The programme was re-installed yesterday and is stable without any updates. I run also windows 10 on this machine but have experienced no problems with display or documents text/ icons ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 1 08:34:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3034] Subsystem: Hewlett-Packard Company Device [103c:3034] InstallationDate: Installed on 2015-10-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Compaq dc7900 Small Form Factor ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=551edabd-9342-4276-8f47-bf3c3b2b5894 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G1 v01.22 dmi.board.asset.tag: CZC9468YXF dmi.board.name: 3031h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC9468YXF dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G1v01.22:bd08/25/2009:svnHewlett-Packard:pnHPCompaqdc7900SmallFormFactor:pvr:rvnHewlett-Packard:rn3031h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7900 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Nov 1 06:50:42 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu vivid -- 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/1512066 Title: Desktop screen and icon corruption Status in xorg package in Ubuntu: New Bug description: This is now the 3 rd time to reinstall 15.10. Previously the 15.04 version has been re-installed. Under 15.04 the problem (bug) was restricted to the desktop background image in that after a few days and new updates loaded the screen became corrupted with the appear
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
The Ubuntu problem reporter now redirects to this bug whenever there's not enough space on the /boot partition to install a new version of the kernel. This has gotten much more common on systems set up since 2014, because Ubuntu now creates a small, separate /boot partition by default. On systems partitioned with earlier versions of Ubuntu /boot is part of a much larger / partition, so you may never run into this. I've included my workaround to this problem, which I'm now using every couple of weeks when one or another of my Ubuntu systems gets into this state. But I also want to disagree with the resolution proposed by the title of this bug. Even if the "fix" proposed in the title of this bug were implemented, it wouldn't solve the problem or even make it easier for less-technical users to get their systems working again. Ubuntu must manage the set of kernels installed on the system. It must set up a /boot partition capable of holding the number of kernels it expects to see on a normal system. If /boot becomes full it must be able to identify and remove some old kernels. Expecting the end user to manage this means Ubuntu is unsuitable for non-technical users, and I think that goes entirely against Ubuntu's founding principles. Moreover, I don't know why even a technically-minded user would be satisfied with the current state of affairs. There's no reason why the package manager should get into a broken state every few weeks that requires human intervention to fix. These old kernels serve no purpose for the great majority of users, technical or not. For those who are running into this for the first time, here's the workaround I use to fix this problem. Be very careful doing this; deleting the wrong thing can easily render your system unbootable. I use aptitude for package management, so you'll need to install it before you can do this (sudo apt-get install aptitude). At a command prompt: $ aptitude search linux-image | grep ^i This will produce a list of installed kernel images, which look like this: i linux-image-3.19.0-28-generic - Linux kernel image for version 3.19.0 on 686 i linux-image-3.19.0-30-generic - Linux kernel image for version 3.19.0 on 686 You can delete all of them, except the most recent one and the one that's actually running, which may or may not be the same. The most recent one will be the last numbered one on the list. You can find out what's actually running by running this command: $ uname -a Linux gh-narcissus 3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To delete the unused kernels, do this: $ sudo aptitude purge linux-image-3.19.0-28-generic You'll can list more than one image on this command line. Aptitude will warn you that it's going to remove linux-image-extra- packages with the same version numbers as the linux-image packages your purging. That's ok, but make sure the list doesn't include linux-image-generic (which will happen if you accidentally put the latest kernel version on the list). This will sometimes fail, if /boot is completely full. In that case, I remove some of the boot files for the unused kernel images manually, and then run the aptitude purge command again: $ sudo rm /boot/initrd.img-3.19.0-28-generic Usually removing one or two is enough that the package manager will be able to run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touc
[Touch-packages] [Bug 1371401] Re: randomly freezing
Apologies, I now realise I should have created a new bug report which I have done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438708 -- 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/1371401 Title: randomly freezing Status in xorg package in Ubuntu: Incomplete Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 22:30:52 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+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 1371401] Re: randomly freezing
Summary === I think I am affected by this same bug, I have all the above systems and get hard lockups with Linux kernel 3.16 every 5 - 15 minutes. Attempted upgrading to (x)ubuntu 14.10 to see if this improved stability and laptop crashed so badly during the upgrade that it broke grub and had to be recovered with ubuntu boot-repair. This alowed the system to boot and I was able to complete configuration with dkpg --configure -a --pending System still crashes every few minutes when running (x)ubuntu 14.10 and about 50% of the time crashes before even reaching the login screen. If I'm lucky attempting to swich VCs will resolve things but the system always crashes eventually and has to be powered off by holiding the power button for 10 seconds or via the magic sysreq key. No other key cominations work. Hardware I also have an Asus laptop with an Nvida card which is what led me to this bug report, the following hardware is present: * Laptop model Asus G750JS (ASUS-NotebookSKU) * GK104M [GeForce GTX 870M] * 4th Gen Core Processor Integrated Graphics Controller (i915 - not used) * BCM4352 802.11ac Wireless Network Adapter * QCA8171 Gigabit Ethernet BIOS/DMI information == I tried flashing the latest BIOS from (http://www.asus.com/Notebooks_Ultrabooks/ASUS_ROG_G750JS/HelpDesk_Download/) but it didn't fix anything. Running the commands listed above gives: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date G750JS.208 07/17/2014 Driver info This problem occurs with both the nouveau and nvidia drivers: rc nvidia-331-updates 331.113-0ubuntu0.0.4 (removed by "additional drivers" application) ii xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 Workaround == This configuration is rock solid on kernel 3.13. I was able to boot to a previously installed kernel (3.13.0-44-generic) and the system performs as expected and is stable. Debug info = I was able to take a photo after the ubuntu system upgrade crashed (attached). The system has been generating a bunch of problem reports too so I've been clicking the submit button. Happy to rovide futher info or try a few experiments to get this resolved. -- 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/1371401 Title: randomly freezing Status in xorg package in Ubuntu: Incomplete Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550J
[Touch-packages] [Bug 1371401] Re: randomly freezing
** Attachment added: "photo of crash message" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+attachment/4361960/+files/20150330_233205_small.jpg -- 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/1371401 Title: randomly freezing Status in xorg package in Ubuntu: Incomplete Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 22:30:52 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+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 1384477] [NEW] install fails: "insserv: ssh: Permission denied"
Public bug reported: Setting up openssh-server (1:6.6p1-8) ... insserv: ssh: Permission denied update-rc.d: error: insserv rejected the script header dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1384477 Title: install fails: "insserv: ssh: Permission denied" Status in “openssh” package in Ubuntu: New Bug description: Setting up openssh-server (1:6.6p1-8) ... insserv: ssh: Permission denied update-rc.d: error: insserv rejected the script header dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1384477/+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
