[Touch-packages] [Bug 1462977] Re: Thinkpad T440s - Sound muted when docked to docking station
if node 0x16 is dock headphone jack, the playback switch should not be line out what is the output jack at docking station ? dock headphone jack or dock line out jack Okay... How can I check this? I am sorry, but I am pretty new to the internals alsa / pulseaudio... I am not sure how can I help you best there to narrow down the issue... -- 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/1462977 Title: Thinkpad T440s - Sound muted when docked to docking station Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi everyone, when I dock my Thinkpad T440s to my docking station, the sound channel for the speakers connected to the docking station audio jack are muted by default. If I run the following command after docking amixer --card 1 sset 'Speaker+LO' 100% the sound starts working. Unfortunatly I have to run this command every time I am docking the system to the docking station. Furthermore there is specific volume slider is not shown in the audio setttings of Unity. So this command could only be a temporary workaround... The internal speakers and the headphones jack of my laptop does not have these problems. It would be really nice if the audio output of the docking stations stays unmuted, when i connect the laptop to the docking station. Maybe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1101386, but the workaround proposed there does not work for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: fabian 2170 F...m pulseaudio /dev/snd/controlC1: fabian 2170 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 8 12:50:20 2015 InstallationDate: Installed on 2015-04-28 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internes Audio - HDA Intel PCH Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQS00600:pvrThinkPadT440s:rvnLENOVO:rn20AQS00600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQS00600 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1462977/+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 1320201] Re: behaviour in debug mode doesn't match real behaviour
I'm not sure if you're waiting for a confirmation from me, but this
patch seems to work perfectly! Merge away :).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1320201
Title:
behaviour in debug mode doesn't match real behaviour
Status in logrotate package in Ubuntu:
Confirmed
Bug description:
Situation: a single log file (no earlier rotates) and a logrotate
status that says it is time to rotate.
# ls -l /var/log/mail.log*
-rw-r- 1 syslog adm 287 May 16 11:27 /var/log/mail.log
# cat /var/lib/logrotate/status
logrotate state -- version 2
/var/log/mail.log 2012-3-31
# cat /tmp/test.conf
/var/log/mail.log
{
rotate 4
weekly
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
reload rsyslog /dev/null 21 || true
endscript
}
logrotate in debug mode will fail, because it simulates removing a
non-existing mail.log.5.gz:
# logrotate -d /tmp/test.conf; echo $?
reading config file /tmp/test.conf
reading config info for /var/log/mail.log
Handling 1 logs
rotating pattern: /var/log/mail.log
weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/mail.log
log needs rotating
rotating log /var/log/mail.log, log-rotateCount is 4
dateext suffix '-20140516'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
previous log /var/log/mail.log.1 does not exist
renaming /var/log/mail.log.4.gz to /var/log/mail.log.5.gz (rotatecount 4,
logstart 1, i 4),
renaming /var/log/mail.log.3.gz to /var/log/mail.log.4.gz (rotatecount 4,
logstart 1, i 3),
renaming /var/log/mail.log.2.gz to /var/log/mail.log.3.gz (rotatecount 4,
logstart 1, i 2),
renaming /var/log/mail.log.1.gz to /var/log/mail.log.2.gz (rotatecount 4,
logstart 1, i 1),
renaming /var/log/mail.log.0.gz to /var/log/mail.log.1.gz (rotatecount 4,
logstart 1, i 0),
renaming /var/log/mail.log to /var/log/mail.log.1
running postrotate script
running script (multiple) with arg /var/log/mail.log
:
reload rsyslog /dev/null 21 || true
removing old log /var/log/mail.log.5.gz
error: error opening /var/log/mail.log.5.gz: No such file or directory
1
logrotate's real behaviour handles this situation correctly:
# logrotate -v /tmp/test.conf; echo $?
reading config file /tmp/test.conf
reading config info for /var/log/mail.log
Handling 1 logs
rotating pattern: /var/log/mail.log
weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/mail.log
log needs rotating
rotating log /var/log/mail.log, log-rotateCount is 4
dateext suffix '-20140516'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
previous log /var/log/mail.log.1 does not exist
renaming /var/log/mail.log.4.gz to /var/log/mail.log.5.gz (rotatecount 4,
logstart 1, i 4),
old log /var/log/mail.log.4.gz does not exist
renaming /var/log/mail.log.3.gz to /var/log/mail.log.4.gz (rotatecount 4,
logstart 1, i 3),
old log /var/log/mail.log.3.gz does not exist
renaming /var/log/mail.log.2.gz to /var/log/mail.log.3.gz (rotatecount 4,
logstart 1, i 2),
old log /var/log/mail.log.2.gz does not exist
renaming /var/log/mail.log.1.gz to /var/log/mail.log.2.gz (rotatecount 4,
logstart 1, i 1),
old log /var/log/mail.log.1.gz does not exist
renaming /var/log/mail.log.0.gz to /var/log/mail.log.1.gz (rotatecount 4,
logstart 1, i 0),
old log /var/log/mail.log.0.gz does not exist
log /var/log/mail.log.5.gz doesn't exist -- won't try to dispose of it
renaming /var/log/mail.log to /var/log/mail.log.1
running postrotate script
0
Summary:
# logrotate -d /tmp/test.conf; echo $?
[..]
removing old log /var/log/mail.log.5.gz
error: error opening /var/log/mail.log.5.gz: No such file or directory
exitcode: 1
# logrotate -v /tmp/test.conf; echo $?
[..]
log /var/log/mail.log.5.gz doesn't exist -- won't try to dispose of it
exitcode: 0
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -
About Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
logrotate:
Installed: 3.7.8-6ubuntu5
Candidate: 3.7.8-6ubuntu5
3) What you expected to happen
debug mode should not output an error and should have exitcode 0
4) What happened instead
debug mode prints an error and has exitcode 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1320201/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON
Hi, did you notice that I wrote that the time jumps ONLY affect CRON entries? No other message shows them, even not the firewall log which receives logs from a Cisco ASA in debug logging mode, so there's A LOT of logs coming in on that channel. -Stefan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON Status in rsyslog package in Ubuntu: Confirmed Bug description: On my main server I see unexplainable time jumps backwards in the syslog. Those jumps affect CRON. Example: Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD ( /storage/exec/status-nostromo.sh /dev/null 21) Feb 7 05:40:01 nostromo CRON[20389]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD ( /storage/exec/checkip.sh 2/dev/null 1/dev/null) For debugging I did the following: Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When CRON logged a wrong time, xclock did NOT show any time jump but seemed to freeze for a fraction of a second. Open a screen and start a script that will once per second read the time (in unix seconds) and compare the read time with the time read a second ago. If the current time was smaller, the script would send an email with a process list from before and after the jump. The script also never detected any time jump. In summary, my current impression is that there might be a bug in CRON because no other programm seems to be able to see the wrong time. The server in question is syslog server for 4 servers and 3 network devices. The time jumps exclusively show in syslog entries from the local CRON instance. Not in any remote syslog entry and not in any other local syslog entry, e.g. from DHCPD, bind, tftpd, etc. etc. Also, after a reboot, things work ok for several days upto about 2 or 3 weeks. Then the time jumps start to occur with increasing frequency. I don't use user crontabs but maintain all jobs in /etc/crontab. I have number of jobs which are triggered every minute and another number of jobs which are triggered every 5 minutes (maybe some CRON internal counter overflow problem?). Hardware: Asus P9D-V Intel Xeon E3-1240L V3 16GB ECC RAM 128GB SSD System 3x3TB ZFS RaidZ2 storage 1x3TB Misc. data CMOS battery already changed and board inspected. nostromo:~ # lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 nostromo:~ # apt-cache policy cron cron: Installed: 3.0pl1-124ubuntu2 Candidate: 3.0pl1-124ubuntu2 Version table: *** 3.0pl1-124ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 1429427] Re: Unexplainable time jumps in CRON
Hi Stefan, yup yup, same here, only showing for cron related entries in syslog. Also somewhat busy due to a noisy sogo/postfix/openchange/dovecot plus all sorts of extra add-ons. Not nearly as noisy as a firewall logging of course ;-) Can you strace your cron pid for a bit, including forks and hopefully confirm it is sending correct dates to syslog? Next you can try then is to strace your rsyslog, which will be very noisy so you best grep for cron related stuff only ;-) Are you using rsyslog? And are you also seeing that xconsole noise? After my rsyslog restart this morning, not seeing any time jumping for cron in syslog just yet, so it's likely also related to something happening over time, like a buffer or other memory related issue. You could try the same, restart rsyslog and see how long it takes for things to start jumping around again... Cheers, GJ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON Status in rsyslog package in Ubuntu: Confirmed Bug description: On my main server I see unexplainable time jumps backwards in the syslog. Those jumps affect CRON. Example: Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD ( /storage/exec/status-nostromo.sh /dev/null 21) Feb 7 05:40:01 nostromo CRON[20389]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD ( /storage/exec/checkip.sh 2/dev/null 1/dev/null) For debugging I did the following: Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When CRON logged a wrong time, xclock did NOT show any time jump but seemed to freeze for a fraction of a second. Open a screen and start a script that will once per second read the time (in unix seconds) and compare the read time with the time read a second ago. If the current time was smaller, the script would send an email with a process list from before and after the jump. The script also never detected any time jump. In summary, my current impression is that there might be a bug in CRON because no other programm seems to be able to see the wrong time. The server in question is syslog server for 4 servers and 3 network devices. The time jumps exclusively show in syslog entries from the local CRON instance. Not in any remote syslog entry and not in any other local syslog entry, e.g. from DHCPD, bind, tftpd, etc. etc. Also, after a reboot, things work ok for several days upto about 2 or 3 weeks. Then the time jumps start to occur with increasing frequency. I don't use user crontabs but maintain all jobs in /etc/crontab. I have number of jobs which are triggered every minute and another number of jobs which are triggered every 5 minutes (maybe some CRON internal counter overflow problem?). Hardware: Asus P9D-V Intel Xeon E3-1240L V3 16GB ECC RAM 128GB SSD System 3x3TB ZFS RaidZ2 storage 1x3TB Misc. data CMOS battery already changed and board inspected. nostromo:~ # lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 nostromo:~ # apt-cache policy cron cron: Installed: 3.0pl1-124ubuntu2 Candidate: 3.0pl1-124ubuntu2 Version table: *** 3.0pl1-124ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 1429427] Re: Unexplainable time jumps in CRON
root@mail1:~# apt-cache policy rsyslog rsyslog: Installed: 7.4.4-1ubuntu2.5 Candidate: 7.4.4-1ubuntu2.6 Version table: 7.4.4-1ubuntu2.6 0 990 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages *** 7.4.4-1ubuntu2.5 0 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.3 0 990 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.4.4-1ubuntu2 0 990 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages So yes I can update, though I doubt that will change anything, except for the rsyslog restart: rsyslog (7.4.4-1ubuntu2.6) trusty-proposed; urgency=medium * debian/usr.sbin.rsyslog: grant read access to /dev/log to cope with behaviorial change of apparmor in utopic HWE kernel (LP: #1425398) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON Status in rsyslog package in Ubuntu: Confirmed Bug description: On my main server I see unexplainable time jumps backwards in the syslog. Those jumps affect CRON. Example: Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD ( /storage/exec/status-nostromo.sh /dev/null 21) Feb 7 05:40:01 nostromo CRON[20389]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD ( /storage/exec/checkip.sh 2/dev/null 1/dev/null) For debugging I did the following: Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When CRON logged a wrong time, xclock did NOT show any time jump but seemed to freeze for a fraction of a second. Open a screen and start a script that will once per second read the time (in unix seconds) and compare the read time with the time read a second ago. If the current time was smaller, the script would send an email with a process list from before and after the jump. The script also never detected any time jump. In summary, my current impression is that there might be a bug in CRON because no other programm seems to be able to see the wrong time. The server in question is syslog server for 4 servers and 3 network devices. The time jumps exclusively show in syslog entries from the local CRON instance. Not in any remote syslog entry and not in any other local syslog entry, e.g. from DHCPD, bind, tftpd, etc. etc. Also, after a reboot, things work ok for several days upto about 2 or 3 weeks. Then the time jumps start to occur with increasing frequency. I don't use user crontabs but maintain all jobs in /etc/crontab. I have number of jobs which are triggered every minute and another number of jobs which are triggered every 5 minutes (maybe some CRON internal counter overflow problem?). Hardware: Asus P9D-V Intel Xeon E3-1240L V3 16GB ECC RAM 128GB SSD System 3x3TB ZFS RaidZ2 storage 1x3TB Misc. data CMOS battery already changed and board inspected. nostromo:~ # lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 nostromo:~ # apt-cache policy cron cron: Installed: 3.0pl1-124ubuntu2 Candidate: 3.0pl1-124ubuntu2 Version table: *** 3.0pl1-124ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 1463327] [NEW] Cannot Lock to Launcher Android Studio icon
Public bug reported: It does not matter if you select Lock to Launcher or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: screenshot.png https://bugs.launchpad.net/bugs/1463327/+attachment/4411955/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1463327 Title: Cannot Lock to Launcher Android Studio icon Status in unity package in Ubuntu: New Bug description: It does not matter if you select Lock to Launcher or not. Upon exiting Android Studio editor, the icon would disappear. Creating the .desktop file manually, also solves the problem only partially: upon clicking on the Android Studio icon, yet another Android Studio icon would appear in the bottom of the Unity bar -- see screenshot attached (look at the icon with a green calipers). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.5+14.04.20150521.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Tue Jun 9 12:20:06 2015 InstallationDate: Installed on 2011-10-23 (1324 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (380 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1463327/+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 1462977] Re: Thinkpad T440s - Sound muted when docked to docking station
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=1c37c22332a2d2c1b4ab32177a4f847c7fe06e38 you have to ask the reporter/author of this patch if it does not work as expected -- 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/1462977 Title: Thinkpad T440s - Sound muted when docked to docking station Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi everyone, when I dock my Thinkpad T440s to my docking station, the sound channel for the speakers connected to the docking station audio jack are muted by default. If I run the following command after docking amixer --card 1 sset 'Speaker+LO' 100% the sound starts working. Unfortunatly I have to run this command every time I am docking the system to the docking station. Furthermore there is specific volume slider is not shown in the audio setttings of Unity. So this command could only be a temporary workaround... The internal speakers and the headphones jack of my laptop does not have these problems. It would be really nice if the audio output of the docking stations stays unmuted, when i connect the laptop to the docking station. Maybe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1101386, but the workaround proposed there does not work for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: fabian 2170 F...m pulseaudio /dev/snd/controlC1: fabian 2170 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 8 12:50:20 2015 InstallationDate: Installed on 2015-04-28 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internes Audio - HDA Intel PCH Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQS00600:pvrThinkPadT440s:rvnLENOVO:rn20AQS00600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQS00600 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1462977/+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 1442607] Re: I can't connect Bq Ubuntu to Ubuntu Store
You can see some dbus error messages in my log. Strangely, after switching locale to US and back it started to work and I wasn't able to reproduce it anymore. ** Attachment added: scope-registry.log.4.gz https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442607/+attachment/4411954/+files/scope-registry.log.4.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1442607 Title: I can't connect Bq Ubuntu to Ubuntu Store Status in unity-scope-click package in Ubuntu: Confirmed Bug description: I had exactly the same issue as described in this thread: https://lists.launchpad.net/ubuntu-phone/msg11847.html In ubuntu store scope I have empty page (just the header 'Ubuntu store' and below a blank page -- see the attached photo). Searching does not change anything - still blank page. The same with refreshing the scope (by pulling the top edge). Other scopes work without problems, and there is no problem with internet connection. I guess that restarting the phone should resolve the issue, but I haven't done this yet. I suspect that the problem occurred when the wi-fi connection was switched on/off - I did it several times (I checked which apps does not work offline) and at some point ubuntu store stopped working. If I can be of some help in debugging the issue please let me know. My phone: BQ Aquaris OS: Ubuntu 14.10 (r20) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442607/+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 1463332] [NEW] zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus!
Public bug reported: get that error logged into journalctl: org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: zeitgeist-datahub 0.9.14-2.2ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Jun 9 11:32:35 2015 SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1463332 Title: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus! Status in zeitgeist package in Ubuntu: New Bug description: get that error logged into journalctl: org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING **: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: zeitgeist-datahub 0.9.14-2.2ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CurrentDesktop: GNOME Date: Tue Jun 9 11:32:35 2015 SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1463332/+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 1419001] Re: Reminders trigger at the time of the event and not before by default
when inserting a new date into LOCAL calendar, having german timezone, entering no data, but saving this date, afterwards it is moved two hours before the entered time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+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 1249333] Re: UbuntuWebView doesn't regard GRID_UNIT_PX
Hi Olivier, Here's a screenshot using a test app with Ubuntu.Web 0.2: http://i.imgur.com/E6Hzq8s.png On the left, started with GRID_UNIT_PX=8, on the right with GRID_UNIT_PX=16 So looks to me as this is still valid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1249333 Title: UbuntuWebView doesn't regard GRID_UNIT_PX Status in Web Browser App: Invalid Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On High-DPI screens like the Apple Retina Display all Ubuntu Components and apps adjust nicely to the DPI by setting the GRID_UNIT_PX env variable. One exception to this is the UbuntuWebView which loads websites very, very tiny on such displays, regardless of the used GRID_UNIT_PX value. The WebView has it's own env variable, QTWEBKIT_DPR, which allows adjusting it's resolution. However, this isn't obvious to users and especially on desktop systems QTWEBKIT_DPR is mostly not set to anything. Couldn't we initialize QTWEBKIT_DPR to a sane value calculated from the GRID_UNIT_PX value in case it is not explicitly set? To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1249333/+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 1249333] Re: UbuntuWebView doesn't regard GRID_UNIT_PX
** Changed in: webbrowser-app (Ubuntu) Assignee: Michael Zanetti (mzanetti) = (unassigned) ** Changed in: webbrowser-app (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1249333 Title: UbuntuWebView doesn't regard GRID_UNIT_PX Status in Web Browser App: Invalid Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On High-DPI screens like the Apple Retina Display all Ubuntu Components and apps adjust nicely to the DPI by setting the GRID_UNIT_PX env variable. One exception to this is the UbuntuWebView which loads websites very, very tiny on such displays, regardless of the used GRID_UNIT_PX value. The WebView has it's own env variable, QTWEBKIT_DPR, which allows adjusting it's resolution. However, this isn't obvious to users and especially on desktop systems QTWEBKIT_DPR is mostly not set to anything. Couldn't we initialize QTWEBKIT_DPR to a sane value calculated from the GRID_UNIT_PX value in case it is not explicitly set? To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1249333/+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 1359486] Re: Use LibreOffice Dialogs setting is ignored in KDE
cleary (bernard-gray), can you post link to your ppa with fixed packages? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: Use LibreOffice Dialogs setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option Use LibreOffice Dialogs is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+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 965371] Re: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04
Workaround for PHP to make it work need to disable SSL check by adding this params to SoapClient stream_context = stream_context_create( array( 'ssl' = array( 'verify_peer' = false, 'verify_peer_name' = false, ) ) ) -- 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/965371 Title: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04 Status in OpenSSL cryptography and SSL/TLS toolkit: Confirmed Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Triaged Status in openssl package in Debian: Fix Released Bug description: This week, HTTPS connections from a Python script I wrote started giving me this error: urllib2.URLError: urlopen error [Errno 8] _ssl.c:497: EOF occurred in violation of protocol This used to work up until some three days ago and still works on other Ubuntu versions, but not in other Python versions on Precise. I was suspecting this was a bug in Python, but a guy on AskUbuntu ( http://askubuntu.com/questions/116020/python-https-requests-urllib2 -to-some-sites-fail-on-ubuntu-12-04-without-proxy/116059#116059 ) found out this happens using the openssl command line tool too: $ openssl s_client -connect www.mediafire.com:443 But succeeds if forcing TLS 1 with the -tls1 argument. To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/965371/+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 1445106] Re: [Notifications] turn the screen on
To answer Oliver's question, iOS prevents pocket presses on notifications by requiring you to slide notifications on the lock screen, not just tap them. There are probably many other sane solutions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1445106 Title: [Notifications] turn the screen on Status in Ubuntu UX bugs: Triaged Status in indicator-messages package in Ubuntu: Confirmed Bug description: Built: r20 When getting a notification, such as a text message, the screen will turn on. This becomes a problem when the device is kept in a pocket, where it may falsely register screen activity and thus stay on for hours. -UX comment- Please refer for the correct behaviour here: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1445106/+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 1426307] Re: location is inaccurate
Hi, maybe I crowed to soon. I rebooted this morning and everything was the same. I always test with the Sensor Status app and an additional app I wrote by myself. I don't get any data by the GPS sensor for about 10 minutes sometimes, sometimes no data at all. My 30€ mobile GPS device works fine. But when I got the GPS fix, the location data is updated very often and everything works as expected. The accuracy of the position is also perfect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate Status in the base for Ubuntu mobile products: Fix Released Status in location-service package in Ubuntu: Fix Released Status in location-service source package in Vivid: New Status in location-service package in Ubuntu RTM: Fix Released Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Location is inaccurate, it thinks that I'm several kilometres away from my actual location, in the middle of the sea. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Fri Feb 27 11:10:42 2015 InstallationDate: Installed on 2015-02-25 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1132736] Re: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg
** Description changed: + Bug: + + The bug happens whenever the remaining configuration files of the + original X stack is removed, ie purging. It does not happen for users + who do not explicitly remove those. + + Workaround: + + For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack + (=14.10/utopic): + + sudo dpkg-reconfigure xserver-xorg-lts-utopic + + This restores the symlink /etc/X11/X - /usr/bin/Xorg + + --- + After installing the hardware enablement stack on precise by running: - sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal + sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing: X: cannot stat /etc/X11/X (No such file or directory), aborting. I updates two computers running precise x86_64 and both had the problem. Just recreating the symlink fixes the problem and then precise runs perfectly fine with the new stack (in fact, it's more stable so far). ** Changed in: xorg (Ubuntu) Assignee: Maarten Lankhorst (mlankhorst) = (unassigned) ** Also affects: xorg-lts-vivid (Ubuntu) Importance: Undecided Status: New -- 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/1132736 Title: Xorg fails to start after installing the hardware enablement stack on precise due to missing symlink after purging old xserver-xorg Status in xorg package in Ubuntu: Triaged Status in xorg-lts-trusty package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Status in xorg-lts-vivid package in Ubuntu: New Bug description: Bug: The bug happens whenever the remaining configuration files of the original X stack is removed, ie purging. It does not happen for users who do not explicitly remove those. Workaround: For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack (=14.10/utopic): sudo dpkg-reconfigure xserver-xorg-lts-utopic This restores the symlink /etc/X11/X - /usr/bin/Xorg --- After installing the hardware enablement stack on precise by running: sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing: X: cannot stat /etc/X11/X (No such file or directory), aborting. I updates two computers running precise x86_64 and both had the problem. Just recreating the symlink fixes the problem and then precise runs perfectly fine with the new stack (in fact, it's more stable so far). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+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 1447146] Re: NetworkManager assertion failure: dir != NULL
Get the same error logged on Wily ** Tags added: wily ** Tags added: i386 -- 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/1447146 Title: NetworkManager assertion failure: dir != NULL Status in network-manager package in Ubuntu: Confirmed Bug description: Here is an error seen in journalctl: Apr 21 22:01:13 xeelee NetworkManager[1493]: (NetworkManager:1493): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 22 14:24:07 2015 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 802-3-ethernet 1429705273 Wed 22 Apr 2015 02:21:13 PM CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1447146/+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 1429427] Re: Unexplainable time jumps in CRON
Gave it another 10 mins, this time checking the 'receiving' end, being
rsyslog in my case:
[pid 583] ... select resumed ) = 1 (in [0])
[pid 583] recvmsg(0, {msg_name(0)=NULL, msg_iov(1)=[{86Jun 9 10:01:01
CRON[4860]: pam_unix(cron:session): session opened for user sogo by (uid=0),
8096}], msg_controllen=64, {cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=0x1d
/* SCM_??? */, ...}, msg_flags=0}, MSG_DONTWAIT) = 95
[pid 583] futex(0x73de74, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x73de70,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} unfinished ...
[pid 585] ... futex resumed ) = 0
[pid 583] ... futex resumed ) = 1
[pid 585] futex(0x73e060, FUTEX_WAIT_PRIVATE, 2, NULL unfinished ...
[pid 583] futex(0x73e060, FUTEX_WAKE_PRIVATE, 1 unfinished ...
[pid 585] ... futex resumed ) = -1 EAGAIN (Resource temporarily
unavailable)
[pid 583] ... futex resumed ) = 0
[pid 585] futex(0x73e060, FUTEX_WAKE_PRIVATE, 1 unfinished ...
[pid 583] select(4, [0 3], NULL, NULL, NULL unfinished ...
[pid 585] ... futex resumed ) = 0
[pid 585] write(5, Jun 9 10:01:01 mail1 CRON[4860]: pam_unix(cron:session):
session opened for user sogo by (uid=0)\n, 98) = 98
[pid 585] write(1, May 30 19:38:01 mail1 CRON[4860]: message repeated 3
times: [ (sogo) CMD (/usr/sbin/sogo-ealarms-notify /usr/sbin/sogo-tool
expire-sessions 60)]\n, 148) = 148
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC) = -1 ENOENT (No
such file or directory)
[pid 585] open(/dev/xconsole, O_RDWR|O_NONBLOCK|O_CLOEXEC unfinished ...
[pid 583] ... select resumed ) = 1 (in [0])
[pid 585] ... open resumed )= -1 ENOENT (No such file or directory)
[pid 583] recvmsg(0, unfinished ...
[pid 585] futex(0x73de74, FUTEX_WAIT_PRIVATE, 2668217, NULL unfinished ...
[pid 583] ... recvmsg resumed {msg_name(0)=NULL, msg_iov(1)=[{78Jun 9
10:01:01 CRON[4861]: (sogo) CMD (/usr/sbin/sogo-ealarms-notify
/usr/sbin/sogo-tool expire-sessions 60), 8096}], msg_controllen=64,
{cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=0x1d /* SCM_??? */, ...},
msg_flags=0}, MSG_DONTWAIT) = 116
[pid 585] ... futex resumed ) = -1 EAGAIN (Resource temporarily
unavailable)
[pid 583] futex(0x73de74, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x73de70,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} unfinished ...
[pid 585] futex(0x73e060, FUTEX_WAIT_PRIVATE, 2, NULL unfinished ...
[pid 583] ... futex resumed ) = 0
[pid 585] ... futex resumed ) = -1 EAGAIN (Resource temporarily
unavailable)
[pid 583] futex(0x73e060, FUTEX_WAKE_PRIVATE, 1 unfinished ...
[pid 585] futex(0x73e060, FUTEX_WAKE_PRIVATE, 1 unfinished ...
[pid 583] ... futex resumed ) = 0
[pid 585] ... futex resumed ) = 0
[pid 583] select(4, [0 3], NULL, NULL, NULL unfinished ...
[pid 585] write(1, Jun 9 10:01:01 mail1 CRON[4861]: (sogo) CMD
(/usr/sbin/sogo-ealarms-notify /usr/sbin/sogo-tool expire-sessions 60)\n,
119) = 119
[pid 585] futex(0x73de74, FUTEX_WAIT_PRIVATE, 2668219, NULL unfinished ...
[pid 583] ... select resumed ) = 1 (in [0])
[pid 583] recvmsg(0, {msg_name(0)=NULL, msg_iov(1)=[{86Jun 9 10:01:01
CRON[4860]: pam_unix(cron:session): session closed for user sogo, 8096}],
msg_controllen=64, {cmsg_len=32, cmsg_level=SOL_SOCKET, cmsg_type=0x1d /*
SCM_??? */, ...}, msg_flags=0}, MSG_DONTWAIT) = 84
[pid 583] futex(0x73de74, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x73de70,
{FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1} unfinished ...
[pid 585] ... futex resumed ) = 0
[pid 583] ... futex resumed ) = 1
[pid 585] futex(0x73e060, FUTEX_WAKE_PRIVATE, 1 unfinished ...
[pid 583] select(4, [0 3], NULL, NULL, NULL unfinished ...
[pid 585] ... futex resumed ) = 0
[pid 585] write(5, Jun 9 10:01:01 mail1 CRON[4860]: pam_unix(cron:session):
session closed for user sogo\n, 87) = 87
[pid 585] futex(0x73de74, FUTEX_WAIT_PRIVATE, 2668221, NULL unfinished ...
From this I can see I need to comment out this darn xconsole in
/etc/rsyslog.d/50-default.conf since this is a vm. But the more
interesting thing is of course:
recvmsg - pam session open - write the same to syslog files
recvmsg - cron cmd - write the
[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON
I'm convinced this is more rsyslog related and not cron. ** Package changed: cron (Ubuntu) = rsyslog (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON Status in rsyslog package in Ubuntu: Confirmed Bug description: On my main server I see unexplainable time jumps backwards in the syslog. Those jumps affect CRON. Example: Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD ( /storage/exec/status-nostromo.sh /dev/null 21) Feb 7 05:40:01 nostromo CRON[20389]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD ( /storage/exec/checkip.sh 2/dev/null 1/dev/null) For debugging I did the following: Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When CRON logged a wrong time, xclock did NOT show any time jump but seemed to freeze for a fraction of a second. Open a screen and start a script that will once per second read the time (in unix seconds) and compare the read time with the time read a second ago. If the current time was smaller, the script would send an email with a process list from before and after the jump. The script also never detected any time jump. In summary, my current impression is that there might be a bug in CRON because no other programm seems to be able to see the wrong time. The server in question is syslog server for 4 servers and 3 network devices. The time jumps exclusively show in syslog entries from the local CRON instance. Not in any remote syslog entry and not in any other local syslog entry, e.g. from DHCPD, bind, tftpd, etc. etc. Also, after a reboot, things work ok for several days upto about 2 or 3 weeks. Then the time jumps start to occur with increasing frequency. I don't use user crontabs but maintain all jobs in /etc/crontab. I have number of jobs which are triggered every minute and another number of jobs which are triggered every 5 minutes (maybe some CRON internal counter overflow problem?). Hardware: Asus P9D-V Intel Xeon E3-1240L V3 16GB ECC RAM 128GB SSD System 3x3TB ZFS RaidZ2 storage 1x3TB Misc. data CMOS battery already changed and board inspected. nostromo:~ # lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 nostromo:~ # apt-cache policy cron cron: Installed: 3.0pl1-124ubuntu2 Candidate: 3.0pl1-124ubuntu2 Version table: *** 3.0pl1-124ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up
This is the patch that fix this issue...
I have been using this patch for almost a year and works perfectly
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
- bootp.yiaddr = dev-ip_addr;
+bootp.yiaddr = INADDR_ANY;
+bootp.flags = htons(0x800);
...
}
I have been talking to Debian people (Daniel Baumann, )who have proved their
complete lack of understanding/interest; they just do not care about this bug.
Talking to them is wasting my time; hopefully Ubuntu will fix this soon.
NOTE:
Please consider ipconfig needs to know (command line parameter)
if your server is of type bootp or dhcp, if this parameter is wrong
ipconfig gives up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
Status in klibc package in Ubuntu:
Confirmed
Status in klibc package in Debian:
New
Bug description:
Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE
boot works normally (PXE Menu, select desired image, image begins
loading), then the boot process hangs while IP-Config attempts to get
an IP address:
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: no response after 2 secs - giving up
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: no response after 3 secs - giving up
These lines appear very quickly (5 seconds has NOT elapsed), after
about a minute, we get this:
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: no response after 4 secs - giving up
Some time later, this:
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: no response after 6 secs - giving up
Until finally, this:
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: no response after 9 secs - giving up
IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
IP-Config: eth0 guessed broadcast address 172.25.11.31
IP-Config: eth0 complete (dhcp from 172.25.10.20):
(snip)
While watching the DHCP server logs, Ubuntu is either not sending a
DHCP Discover at times, or is not replying back with a DHCPRequest
during these sessions, presumably ignoring an response from the DHCP
server. From the initial booting of the system via PXE, to when
Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.
I am seeing this same behavior on both 12.04.3 and 14.04. After
finding a number of similar erros via Google and no real resolution, I
have opened this bug.
The system experiencing this issue has multiple ethernet interfaces
(actual HW, not a VM), some Google found solutions suggest hard coding
DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
acceptable as a system attempting to PXE boot may be using an
alternate port for the network.
I have found what looks to be a very similar bug filed for Debian,
#584583, which also contains a patch for this issue (under Debian).
I have no problems in PXE booting to various Windows, RedHat, Centos,
or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot
at present.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.340
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Jun 6 20:22:09 2014
LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+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 1455788] Re: key is repeated, but keyboard does not send scancodessssssss
Weinga-Unity, to see if this is already fixed in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: latest-bios-f09 ** 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/1455788 Title: key is repeated, but keyboard does not send scancode Status in xorg package in Ubuntu: Incomplete Bug description: I have found the repeat-key and stuck-key issue in different bug-reports but no working solution. My problem is, that sometimes a key is stuck within software and the character is printed in the rate configure for the keyboard. catch of KeyPress event, KeyRelease event sequence with l with xev, f is pressed to stop sequence: c KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 632900, (38,-8), root:(632,311), state 0x100, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XmbLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XmbLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633481, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633500, (38,-8), root:(632,311), state 0x0, keycode 41 (keysym 0x66, f), same_screen YES, XLookupString gives 1 bytes: (66) f XmbLookupString gives 1 bytes: (66) f XFilterEvent returns: False showkey does not print any scancodes: ~$ sudo showkey -s KB-Modus war ?UNBEKANNT? [ Wenn Sie das unter X probieren, muss es nicht funktionieren, da der X Server ebenfalls von /dev/console liest. ] Drücken Sie eine Taste (Programmende 10 s nach dem letzten Tastendruck)... 0x9c 0x20 0xa0 .. 0x20 0x21 0xa0 0x21 0xa1 0x31 0xb1 0x2d 0x2f 0xad 0xaf 0x24 0x26 0xa4 0x26 0x26=l pressed, 0xa6=l released 0xa6 0x21 0xa10x21=f pressed, 0xa1=f released == === uname -or 3.16.0-30-generic GNU/Linux Description: Ubuntu 14.04.2 LTS Release: 14.04 Netbook Gigabyte T1005 CPU Intel Atom N570 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] InstallationDate: Installed on 2015-05-01 (36 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1249): WARNING **: Failed to load user image: Datei »/home/klaus/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden init: indicator-power-main-Prozess (1392) wurde von TERM-Signal beendet init: indicator-application-main-Prozess (1398) wurde mit dem Status 1 beendet MachineType: GIGABYTE T1005M/P Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/xubuntu--vg-root ro clocksource=acpi_pm quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Tags: trusty ubuntu Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/30/2010 dmi.bios.vendor: GIGABYTE dmi.bios.version: F09 dmi.board.asset.tag: Base Board Asset
[Touch-packages] [Bug 1444402] Re: LXC with r/w sys and udev keeps trying to unmount bind mounts
Confirmed the fix on a cloud VM, thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- 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/102 Title: LXC with r/w sys and udev keeps trying to unmount bind mounts Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Bug description: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? SRU TEST CASE: -- - Create a vivid container, and set lxc.aa_profile = unconfined and lxc.mount.auto = sys:rw cgroup in its config. (Note that the latter is not supported!) - Start the container - Run mount -v -o bind /bin /mnt - Observe that it doesn't stay mounted, but sudo journalctl says Mai 06 09:17:08 test systemd[1]: Unit mnt.mount is bound to inactive unit dev-sda3.device. Stopping, too. Mai 06 09:17:08 test systemd[1]: Unmounting /mnt... Mai 06 09:17:08 test systemd[1]: Unmounted /mnt. - With the fixed package bind mounts stay mounted. REGRESSION POTENTIAL: This could potentially break cleanup of stale mount points of either hotplug devices which disappear, or media which get forcefully ejected (like CDs). Testing should include that these still work. laney@vivid apt-cache policy systemd systemd: Installed: 219-7ubuntu1 Candidate: 219-7ubuntu1 Version table: *** 219-7ubuntu1 0 500 http://sherwood/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/102/+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 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
** Also affects: ubuntu-translations Importance: Undecided Status: New ** Changed in: ubuntu-translations Assignee: (unassigned) = Ubuntu Portuguese Translators (ubuntu-l10n-pt) -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in Ubuntu Translations: New Status in software-properties package in Ubuntu: Confirmed Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The big tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1377742/+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 1457754] Re: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New = Confirmed -- 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/1457754 Title: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1 Status in apt package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0 -gui-in-containers/ + https://www.stgraber.org/2014/01/17/lxc-1-0 -unprivileged-containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1457754/+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 1457754] Re: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/1457754 Title: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1 Status in apt package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0 -gui-in-containers/ + https://www.stgraber.org/2014/01/17/lxc-1-0 -unprivileged-containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1457754/+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 1463370] [NEW] Keyboard autorepeat missing
Public bug reported: Using Unity8 (8.02+15.04.20150409.1-0ubuntu1) on a desktop from this image http://cdimage.ubuntu.com/ubuntu-desktop-next/backup-20150422/ Apps (terminal, messaging and others) have no keyboard auto-repeat. This makes keyboard navigation and backspace slow and cumbersome. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1463370 Title: Keyboard autorepeat missing Status in unity8 package in Ubuntu: New Bug description: Using Unity8 (8.02+15.04.20150409.1-0ubuntu1) on a desktop from this image http://cdimage.ubuntu.com/ubuntu-desktop-next/backup-20150422/ Apps (terminal, messaging and others) have no keyboard auto-repeat. This makes keyboard navigation and backspace slow and cumbersome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1463370/+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 1463376] [NEW] Google account needs re-authorization
You have been subscribed to a public bug: I have set up a Google account in Online Accounts app. Every few weeks there is a notification that applications can no longer access it and it needs re-authorization. I don't know if this is by design. When I set up the account, Ubuntu should remember it forever until I disable the account or change my credentials in Google. It is bad usability that the account must be re-authorized and causes users not to use the feature. I understand this increases security, but mandatory re-authorization every few weeks is way too often from user's point of view. ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New -- Google account needs re-authorization https://bugs.launchpad.net/bugs/1463376 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings-online-accounts 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 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
I've added the Ubuntu Translations project to track the fixing of the Portuguese translation in 14.04 specifically. This particular problem seems to have been fixed in the code, but there are a couple of other places where bigb or bbig are needlessly left vulnerable to mistakes by translators. I've made a branch to fix those. ** Branch linked: lp:~mpt/software-properties/1377742-markup ** Changed in: software-properties (Ubuntu) Status: Confirmed = In Progress -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in Ubuntu Translations: Fix Committed Status in software-properties package in Ubuntu: In Progress Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The big tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1377742/+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 1438046] Re: Can't download protected images
Now that context menu support has landed in oxide (bug #1326070), link targets and media (images, video, audio, …) can be downloaded from the context menu with a call to saveLink()/saveMedia(), which will trigger the downloadRequested signal with the necessary data (cookies and referrer). ** No longer affects: webbrowser-app ** No longer affects: oxide ** No longer affects: content-hub (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1438046 Title: Can't download protected images Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: In the webbrowser app I login to a site (https://slack.com) which has private image sharing. Under every image there is a link, named 'Open original' that links to the image itself (like https://files.slack.com/files-pri/T02A1MKNL- F046U9A6V/img_20150328_103844.jpg). But to see the image you've to login to the website. So, when you try to download it (long press - save image) the browser calls the content hub, and indeed content hub saves img_20150328_103844.jpg in ~/Pictures, but the file is an .html file, and not the image, so the photo doesn't appear in the gallery app. The first thing IMO is to display an error if the file isn't valid, because it took me a while understand what was wrong with my dowload - it says 'Success' but then my photo isn't in the gallery. Then, there should be a way to download private resources from the web To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1438046/+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 1457754] Re: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1
I'm getting this on regular installation of Ubuntu 15.10: nazar-pc@nazar-pc ~ sudo apt-get update Hit http://repository.spotify.com stable InRelease Ign http://ua.archive.ubuntu.com wily InRelease Get:1 http://repository.spotify.com stable/non-free amd64 Packages [1 433 B] Ign http://download.opensuse.org InRelease Hit http://repo.steampowered.com precise InRelease Ign http://ppa.launchpad.net vivid InRelease Ign http://extras.ubuntu.com utopic InRelease Ign http://archive.canonical.com wily InRelease Hit http://repository.spotify.com stable/non-free i386 Packages Ign http://ua.archive.ubuntu.com wily-updates InRelease Hit http://download.opensuse.org Release.gpg Ign http://ppa.launchpad.net vivid InRelease Hit http://extras.ubuntu.com utopic Release.gpg Ign http://ua.archive.ubuntu.com wily-backports InRelease Hit http://archive.canonical.com wily Release.gpg Ign http://security.ubuntu.com wily-security InRelease Hit http://download.opensuse.org Release Hit http://dl.hhvm.com vivid InRelease Ign http://ua.archive.ubuntu.com wily-proposed InRelease Ign http://ppa.launchpad.net vivid InRelease Hit http://extras.ubuntu.com utopic Release Hit http://archive.canonical.com wily Release Get:2 http://ua.archive.ubuntu.com wily Release.gpg [933 B] Ign http://ppa.launchpad.net wily InRelease Ign http://repository.spotify.com stable/non-free Translation-en
[Touch-packages] [Bug 1463376] Re: Google account needs re-authorization
Hi Ville, thanks for reporting this bug. Can you please tell me what version of Ubuntu you are using? Also, when you go to reauthorize the account, and you click on the Grant authorization button, what do you see? Could you please take a screenshot of that window and attach it to this bug report? ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1463376 Title: Google account needs re-authorization Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: I have set up a Google account in Online Accounts app. Every few weeks there is a notification that applications can no longer access it and it needs re-authorization. I don't know if this is by design. When I set up the account, Ubuntu should remember it forever until I disable the account or change my credentials in Google. It is bad usability that the account must be re-authorized and causes users not to use the feature. I understand this increases security, but mandatory re-authorization every few weeks is way too often from user's point of view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1463376/+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 1463353] [NEW] Notifications not translated on first boot
Public bug reported: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: qa-silo ** Attachment added: screenshot20150609_101611687.png https://bugs.launchpad.net/bugs/1463353/+attachment/4411997/+files/screenshot20150609_101611687.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1463353 Title: Notifications not translated on first boot Status in indicator-messages package in Ubuntu: New Bug description: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1463353/+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 1457754] Re: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1
Bug appears after updating curl from 7.38.0-3ubuntu3 to 7.42.1-2ubuntu1. Downgrading to 7.38.0-3ubuntu3 fixes the problem ** Also affects: curl Importance: Undecided Status: 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/1457754 Title: E: Method http has died unexpectedly when run under lxc on wily apt 1.0.9.9ubuntu1 Status in Curl - transfer files with URL syntax: New Status in apt package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: lxc-create -t download -n wily-gui -- -d ubuntu -r wily -a amd64 + some config according to https://www.stgraber.org/2014/02/09/lxc-1-0 -gui-in-containers/ + https://www.stgraber.org/2014/01/17/lxc-1-0 -unprivileged-containers/ + enabling network. --- root@wily-gui:/home/ubuntu# apt update E: Method http has died unexpectedly! E: Sub-process http received a segmentation fault. --- Downgrading apt to https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4 in the LXC rootfs seems to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/curl/+bug/1457754/+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 1463353] Re: Notifications not translated on first boot
Probably the locale is not correctly propagated to all the programs, so it's not a problem of indicator-messages, but of the installation wizard. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1463353 Title: Notifications not translated on first boot Status in indicator-messages package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Needs a krillin with SD card and working SIM card. Test case. - Flash a new image. - Complete the installation wizard. - Make a call to the device (missed one). - Open the notification indicator. Expected result. - SD Card and missed call notifications are not translated on first boot. After rebooting the phone, the notifications appear translated. current build number: 28 device name: krillin channel: rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1463353/+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 1455788] Re: key is repeated, but keyboard does not send scancodessssssss
Same Problem with wily version. See Screenshot. ** Attachment added: IMG_20150609_120030.jpg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455788/+attachment/4411987/+files/IMG_20150609_120030.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/1455788 Title: key is repeated, but keyboard does not send scancode Status in xorg package in Ubuntu: Incomplete Bug description: I have found the repeat-key and stuck-key issue in different bug-reports but no working solution. My problem is, that sometimes a key is stuck within software and the character is printed in the rate configure for the keyboard. catch of KeyPress event, KeyRelease event sequence with l with xev, f is pressed to stop sequence: c KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 632900, (38,-8), root:(632,311), state 0x100, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XmbLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633234, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XmbLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633481, (38,-8), root:(632,311), state 0x0, keycode 46 (keysym 0x6c, l), same_screen YES, XLookupString gives 1 bytes: (6c) l XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x2e1, root 0x7e, subw 0x0, time 633500, (38,-8), root:(632,311), state 0x0, keycode 41 (keysym 0x66, f), same_screen YES, XLookupString gives 1 bytes: (66) f XmbLookupString gives 1 bytes: (66) f XFilterEvent returns: False showkey does not print any scancodes: ~$ sudo showkey -s KB-Modus war ?UNBEKANNT? [ Wenn Sie das unter X probieren, muss es nicht funktionieren, da der X Server ebenfalls von /dev/console liest. ] Drücken Sie eine Taste (Programmende 10 s nach dem letzten Tastendruck)... 0x9c 0x20 0xa0 .. 0x20 0x21 0xa0 0x21 0xa1 0x31 0xb1 0x2d 0x2f 0xad 0xaf 0x24 0x26 0xa4 0x26 0x26=l pressed, 0xa6=l released 0xa6 0x21 0xa10x21=f pressed, 0xa1=f released == === uname -or 3.16.0-30-generic GNU/Linux Description: Ubuntu 14.04.2 LTS Release: 14.04 Netbook Gigabyte T1005 CPU Intel Atom N570 --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] Subsystem: Gigabyte Technology Co., Ltd Device [1458:b100] InstallationDate: Installed on 2015-05-01 (36 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1249): WARNING **: Failed to load user image: Datei »/home/klaus/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden init: indicator-power-main-Prozess (1392) wurde von TERM-Signal beendet init: indicator-application-main-Prozess (1398) wurde mit dem Status 1 beendet MachineType: GIGABYTE T1005M/P Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/xubuntu--vg-root ro clocksource=acpi_pm quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Tags: trusty ubuntu Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/30/2010 dmi.bios.vendor: GIGABYTE dmi.bios.version: F09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: T1005M/P
[Touch-packages] [Bug 932225] Re: logrotate cron script fails for logs with a space
Hi guys, Any news about that fix? We we it in production with no issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/932225 Title: logrotate cron script fails for logs with a space Status in logrotate package in Ubuntu: New Bug description: /etc/cron.daily has a script called logrotate which will kick off logrotate. Before logrotate is executed, the script scans the logrotate status file, located in /var/lib/logrotate/status to search for non-existant files and remove them from the status file. This script is written in a way which assumes all log files will not have spaces in their name, causing logrotate not to be passed these log files for rotation. The sequence of events is: 1) logrotate bash script starts, starting logrote, which looks into /etc/logrotate.d for logrotate configuration files. It inserts the relevant log file names into /var/lib/logrotate/status. On first detection of the log type, logrotate will not rotate the log. 2) Once one hour has passed, cron calls the logrotate bash script again. It scans /var/lib/logrotate/status for non-existant files. It is unable to parse a log file with a space in the name, and assumes the log file does not exist. It then removes the log from the status file. 3) logrotate starts, and as it does not have an entry for the log, adds it back into the status file, but does not rotate (same as 1) ) Attached is a patch - a replacement logrotate cron script. - Ubuntu Server 11.04 Natty x64 logrotate 3.7.8-6ubuntu3.1 cron 3.0pl1-116ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/932225/+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 1463376] Re: Google account needs re-authorization
I hope this is the correct package for the bug. Change to more suitable one if needed. ** Package changed: ubuntu = ubuntu-system-settings-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1463376 Title: Google account needs re-authorization Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: I have set up a Google account in Online Accounts app. Every few weeks there is a notification that applications can no longer access it and it needs re-authorization. I don't know if this is by design. When I set up the account, Ubuntu should remember it forever until I disable the account or change my credentials in Google. It is bad usability that the account must be re-authorized and causes users not to use the feature. I understand this increases security, but mandatory re-authorization every few weeks is way too often from user's point of view. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1463376/+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 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
All the bigb or bbig were removed from pt_PT. Probably was a translation error from English. -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in Ubuntu Translations: Fix Committed Status in software-properties package in Ubuntu: In Progress Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The big tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1377742/+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 1463264] Re: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: Confirmed Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 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/1463264/+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 1463262] Re: black video thumbnails
It looks like the gallery app times out after a while and then displays the missing art icon. It shouldn't be doing that. On the initial load of the app with a cold cache, we need to thumbnail loads of photos and videos. On a Mako, that takes quite some time. We are parallelizing this as much as possible already but, if there are many videos, the last one can take more than 30 seconds to show up. The thumbnailer *will* eventually come up with a thumbnail, so there is no point in timing out in the calling app. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1463262 Title: black video thumbnails Status in Thumbnail generator for all kinds of files: New Status in gallery-app package in Ubuntu: New Bug description: I have about 30 photos and 30 videos on the phone. When starting the gallery app, I scroll the carousel all the way to the right, to force all thumbnails to be loaded. (That's while there are still lots of spinners shown.) All the videos appear at the right- hand end of the carousel. Most of them have good thumbnails but, randomly, a few of them show a black thumbnail. Looking in the cache, we do not report any failures or other errors. When looking at the cache with thumbnailer-admin, I see that we have cached a completely black image in the full-size cache. The only way for that to happen is if vs-thumb gives us a black thumbnail without reporting an error. Looks like streamer is to blame. (I'm seeing this with two concurrent vs-thumbs running.) To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1463262/+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 1463264] Re: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
I have also faced the same issue of application closing after Unlock using Ubuntu 14.04.01 on HP ProBook 450 G2 Rahat Ali Khan -- 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/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: Confirmed Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 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/1463264/+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 1463264] Re: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
same issue with 14.04.1 on hp probook g2 64bit -- 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/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: Confirmed Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 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/1463264/+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 1463262] Re: black video thumbnails
The attached screenshot shows both problems. Interestingly, when I scroll the carousel left, so the three default icons are no longer visible, and the scroll right again, the correct thumbnails appear. The cache reports that these were produced from a hit. This strongly suggests that the default icon that is displayed is incorrectly produced by the gallery app. ** Also affects: gallery-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1463262 Title: black video thumbnails Status in Thumbnail generator for all kinds of files: New Status in gallery-app package in Ubuntu: New Bug description: I have about 30 photos and 30 videos on the phone. When starting the gallery app, I scroll the carousel all the way to the right, to force all thumbnails to be loaded. (That's while there are still lots of spinners shown.) All the videos appear at the right- hand end of the carousel. Most of them have good thumbnails but, randomly, a few of them show a black thumbnail. Looking in the cache, we do not report any failures or other errors. When looking at the cache with thumbnailer-admin, I see that we have cached a completely black image in the full-size cache. The only way for that to happen is if vs-thumb gives us a black thumbnail without reporting an error. Looks like streamer is to blame. (I'm seeing this with two concurrent vs-thumbs running.) To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1463262/+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 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386111 Title: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04 Status in Unity: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Status in qtbase package in Ubuntu: Confirmed Status in texmaker package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for searching ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: texmaker 4.3-1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 11:01:56 2014 InstallationDate: Installed on 2014-04-18 (191 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: texmaker UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386111/+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 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04
The short-cuts seem to work in tty7 but the gnome-shell is running in tty2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386111 Title: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04 Status in Unity: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Status in qtbase package in Ubuntu: Confirmed Status in texmaker package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for searching ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: texmaker 4.3-1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 27 11:01:56 2014 InstallationDate: Installed on 2014-04-18 (191 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: texmaker UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386111/+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 1459143] Re: Complete system freeze upon switching WiFi networks
Hi. I have the same problem. I am using Ubuntu 15.04 with GNOME. -- 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/1459143 Title: Complete system freeze upon switching WiFi networks Status in network-manager package in Ubuntu: Confirmed Bug description: Occasionally when I am manually switching from one WiFi network to another through the Indicator applet, the entire system freezes completely—neither the laptop's own keyboard and trackpad nor any USB devices produce any effect. The only way to resolve the situation is then to force a power down, which has caused me to lose data on several occasions. This started occurring on Xubuntu 15.04; I have not had any similar bugs on previous iterations of Xubuntu or other Ubuntu variants. It seems to happen when I am switching from an unsecured to a particular WPA-secured WiFi network, though as it happens only once in a while (about once every two days or so under moderate computer use) I am not sure about the source of the issue. I do know that it seems to happen only while switching WiFi networks. This is one of two new network-manager bugs that I noticed around the same time, immediately after upgrading to 15.04. The other bug was https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1270257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1459143/+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 1459143] Re: Complete system freeze upon switching WiFi networks
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = 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/1459143 Title: Complete system freeze upon switching WiFi networks Status in network-manager package in Ubuntu: Confirmed Bug description: Occasionally when I am manually switching from one WiFi network to another through the Indicator applet, the entire system freezes completely—neither the laptop's own keyboard and trackpad nor any USB devices produce any effect. The only way to resolve the situation is then to force a power down, which has caused me to lose data on several occasions. This started occurring on Xubuntu 15.04; I have not had any similar bugs on previous iterations of Xubuntu or other Ubuntu variants. It seems to happen when I am switching from an unsecured to a particular WPA-secured WiFi network, though as it happens only once in a while (about once every two days or so under moderate computer use) I am not sure about the source of the issue. I do know that it seems to happen only while switching WiFi networks. This is one of two new network-manager bugs that I noticed around the same time, immediately after upgrading to 15.04. The other bug was https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1270257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1459143/+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 1463264] Re: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
I am having this issue from past more then 30+ Days. I tried many workarounds but point to mention is my output suffers a lot due to this issue. @Admin: Please also rate the effective panic creating ranking as well. I have Ubuntu 14.04 kernel 3.13.0-53-generic #89-Ubuntu SMP -- 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/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: Confirmed Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 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/1463264/+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 1439701] Re: Autopilot tests for the ubuntu ui tk are failing
This bug was fixed in the package ubuntu-html5-theme - 0.1.2+15.10.20150604-0ubuntu1 --- ubuntu-html5-theme (0.1.2+15.10.20150604-0ubuntu1) wily; urgency=medium [ Alexandre Abreu ] * Fix AP tests and tab selection issue (LP: #1439701) [ CI Train Bot ] * New rebuild forced. -- CI Train Bot ci-train-...@canonical.com Thu, 04 Jun 2015 21:56:30 + ** Changed in: ubuntu-html5-theme (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-html5-theme in Ubuntu. https://bugs.launchpad.net/bugs/1439701 Title: Autopilot tests for the ubuntu ui tk are failing Status in Ubuntu UI SDK for HTML5 Apps: In Progress Status in ubuntu-html5-theme package in Ubuntu: Fix Released Bug description: Autopilot tests for the ubuntu ui tk are failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-html5-theme/+bug/1439701/+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 1426307] Re: location is inaccurate
Hi Lucio :) Are you talking about the time that the GPS takes for get accuracy? Please, could you confirm me if the Sensor Status app (from the Store) works in the same way too? Best regards and thanks in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate Status in the base for Ubuntu mobile products: Fix Released Status in location-service package in Ubuntu: Fix Released Status in location-service source package in Vivid: New Status in location-service package in Ubuntu RTM: Fix Released Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Location is inaccurate, it thinks that I'm several kilometres away from my actual location, in the middle of the sea. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Fri Feb 27 11:10:42 2015 InstallationDate: Installed on 2015-02-25 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1407220] Re: clock is sometimes missing in notification area
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1407220 Title: clock is sometimes missing in notification area Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After startup the clock in the notification area is sometimes missing. It looks quite random when the clock is missing and when not. The bug is similar to bug#1239710, but as comment #67 says. This bug is for the phone and I am running the desktop version of ubuntu 14.04 (x64). That is why a new bug report should be created. A workaround for the bug is to kill the indicator-datetime. It will be restarted and the clock will be visible after that. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: tbs6982fe tbs6680fe tbs6923fe tbs6985se tbs6928se tbs6982se tbs6991fe tbs6618fe tbs6983fe tbs6922fe tbs6928fe tbs6991se tbs6290fe wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 3 10:23:40 2015 InstallationDate: Installed on 2014-03-30 (278 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140329) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1407220/+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 1459143] Re: Complete system freeze upon switching WiFi networks
Excellent. I am using the Dell XPS 13, the 2015 edition (model number 9343). I am using the stock Ubuntu GNOME 15.04 installation with, broadcom drivers (bcmwl kernel source), and the windows driver for bluetooth. Please let me know what other information is needed -- 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/1459143 Title: Complete system freeze upon switching WiFi networks Status in network-manager package in Ubuntu: Confirmed Bug description: Occasionally when I am manually switching from one WiFi network to another through the Indicator applet, the entire system freezes completely—neither the laptop's own keyboard and trackpad nor any USB devices produce any effect. The only way to resolve the situation is then to force a power down, which has caused me to lose data on several occasions. This started occurring on Xubuntu 15.04; I have not had any similar bugs on previous iterations of Xubuntu or other Ubuntu variants. It seems to happen when I am switching from an unsecured to a particular WPA-secured WiFi network, though as it happens only once in a while (about once every two days or so under moderate computer use) I am not sure about the source of the issue. I do know that it seems to happen only while switching WiFi networks. This is one of two new network-manager bugs that I noticed around the same time, immediately after upgrading to 15.04. The other bug was https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1270257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1459143/+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 1463238] Re: luks / encrypted volume can not be closed
** Summary changed: - lukes / encrypted volume can not be closed + luks / encrypted volume can not be closed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1463238 Title: luks / encrypted volume can not be closed Status in udisks2 package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: If you install ubuntu with the default full disk encryption option, it creates a partition as a luks container holding an lvm physical volume, which holds two logical volumes: one for root and one for swap. If you boot the livecd, it shows an encrypted disk icon on the unity launcher. Clicking this icon prompts for the luks password and then opens it, and the lvm inside is automatically mounted. The encrypted physical volume vanishes from the unity launcher and the contained root partition is auto mounted. Unmounting this partition still leaves the luks volume unlocked so you can remount it without having to supply the encryption password. Using the gnome disks utility to unlock the luks volume causes it to show up as if it is a sub-partition of the luks partition, and trying to click the lock icon to close the luks volume results in a giant error dialog because it is in use by the lvm volumes. It should be smart enough to deactivate the vg contained in the luks volume so it can then deactivate the luks volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1463238/+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 1429427] Re: Unexplainable time jumps in CRON
I don't get to anything meaningful before the weekend. Gosh, it's at least 10 years since I last straced anything - have to read up on that too. Jup, I'm using rsyslog. I'll keep an eye on xconsole stuff but IIRC I disabled that in rsyslogd.conf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1429427 Title: Unexplainable time jumps in CRON Status in rsyslog package in Ubuntu: Confirmed Bug description: On my main server I see unexplainable time jumps backwards in the syslog. Those jumps affect CRON. Example: Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD ( /storage/exec/status-nostromo.sh /dev/null 21) Feb 7 05:40:01 nostromo CRON[20389]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD ( /storage/exec/checkinternet.sh 2/dev/null 1/dev/null) Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD ( /storage/exec/checkip.sh 2/dev/null 1/dev/null) For debugging I did the following: Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When CRON logged a wrong time, xclock did NOT show any time jump but seemed to freeze for a fraction of a second. Open a screen and start a script that will once per second read the time (in unix seconds) and compare the read time with the time read a second ago. If the current time was smaller, the script would send an email with a process list from before and after the jump. The script also never detected any time jump. In summary, my current impression is that there might be a bug in CRON because no other programm seems to be able to see the wrong time. The server in question is syslog server for 4 servers and 3 network devices. The time jumps exclusively show in syslog entries from the local CRON instance. Not in any remote syslog entry and not in any other local syslog entry, e.g. from DHCPD, bind, tftpd, etc. etc. Also, after a reboot, things work ok for several days upto about 2 or 3 weeks. Then the time jumps start to occur with increasing frequency. I don't use user crontabs but maintain all jobs in /etc/crontab. I have number of jobs which are triggered every minute and another number of jobs which are triggered every 5 minutes (maybe some CRON internal counter overflow problem?). Hardware: Asus P9D-V Intel Xeon E3-1240L V3 16GB ECC RAM 128GB SSD System 3x3TB ZFS RaidZ2 storage 1x3TB Misc. data CMOS battery already changed and board inspected. nostromo:~ # lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 nostromo:~ # apt-cache policy cron cron: Installed: 3.0pl1-124ubuntu2 Candidate: 3.0pl1-124ubuntu2 Version table: *** 3.0pl1-124ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 1463013] Re: geis FTBFS with clang instead of gcc
This bug was fixed in the package geis - 2.2.16+15.10.20150609-0ubuntu1 --- geis (2.2.16+15.10.20150609-0ubuntu1) wily; urgency=medium [ Stephen M. Webb ] * Avoid setting the timestamp in Doxygen-generated documentation so the builds on Debian will be reproduceable. (LP: #1462829) * fix errors reported when build with clang (LP: #1463013) -- CI Train Bot ci-train-...@canonical.com Tue, 09 Jun 2015 10:29:27 + ** Changed in: geis (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geis in Ubuntu. https://bugs.launchpad.net/bugs/1463013 Title: geis FTBFS with clang instead of gcc Status in Open Input Framework Geis C API: In Progress Status in geis package in Ubuntu: Fix Released Status in geis package in Debian: Confirmed Bug description: Using the rebuild infrastructure, your package fails to build with clang (instead of gcc). See build logs here: http://clang.debian.net/logs/2014-01-14/geis_2.2.16-1_unstable_clang.log To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/1463013/+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 1361864] Re: add Preferred property to ConnectionContext interface
** Changed in: network-manager (Ubuntu RTM) Assignee: (unassigned) = Tony Espy (awe) -- 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/1361864 Title: add Preferred property to ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: In Progress Status in ofono package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Status in network-manager package in Ubuntu RTM: In Progress Status in nuntium package in Ubuntu RTM: In Progress Status in ofono package in Ubuntu RTM: In Progress Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+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 1440917] Re: ofono read_contexts code needs some re-work
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Tony Espy (awe) ** Changed in: network-manager (Ubuntu) Importance: Undecided = High -- 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/1440917 Title: ofono read_contexts code needs some re-work Status in network-manager package in Ubuntu: New Bug description: This bug is bring reported as of network-manager version 0.9.10.0-4ubuntu13 ( latest in vivid at bug filing time ). The code in src/devices/wwan/nm-modem-ofono.c needs some optimization. Currently, the function ofono_read_contexts() is triggered when the modem becoming enabled, which happens when the three private boolean flags modem_online, gprs_powered, and gprs_attached are all TRUE, or when a new context is detected via a 'ContextAdded' signal sent by ofono's ConnectionManager interface. This function in turn, synchronously reads ( with a 2s timeout ) the ConnectionManager's 'SubscriberIdentity' property ( aka 'IMSI' ), and then calls the DBus method com.canonical.NMOfono.ReadImsiContexts, which triggers the ofono plugin to re-read the contexts directly from ofono's gprs settings file ( found in /var/lib/ofono/IMSI/ ). This could be optimized by instead having NM read the IMSI whenever the ConnectionManager's 'Powered' property is set, caching the value, and watching for changes to the 'SubscriberIdentity'. Also it's curious that the contexts aren't re-read when a 'ContextRemoved' signal is received. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1440917/+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 1441623] Re: optimize ofono context property-changed logic
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Tony Espy (awe) ** Changed in: network-manager (Ubuntu) Importance: Undecided = High -- 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/1441623 Title: optimize ofono context property-changed logic Status in network-manager package in Ubuntu: New Bug description: This bug is bring reported as of network-manager version 0.9.10.0-4ubuntu13 ( latest in vivid at bug filing time ). The code in src/devices/wwan/nm-modem-ofono.c which handles context property_change signals should be optimized. The function context_properties_changed() watches for key == 'Settings', and then calls ofono_context_get_ip_properties(). This function then calls dbus_g_proxy_call_with_timeout() to invoke the 'GetProperties' method of the context interface. This is a synchronous DBus call which really isn't necessary as the payload for the 'PropertyChanged' signal already contained the required data ( ie. the IP settings ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441623/+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 1462664] Re: Geolocation app is freezing in a few mobiles
Yesterday I had 4 freeze error (with needing to restart the app) and 3 times with no problems. The freeze errors always happened when driving in a town, not on the road. So I think what Edwin says is possible. I have a question: It is necessary to have 3G all the time or the app has the ability to work with just the GPS signal (without refresh the map)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1462664 Title: Geolocation app is freezing in a few mobiles Status in uNAV: New Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu RTM: New Bug description: Hi! With the app GPS Navigation a few users have problem with a freeze issue, because of 100% CPU usage or heavy swap usage (I don't know, because I can't reproduce it. For some users, it is working perfect, for other is freezing after a few minutes. You can see here the user reviews: https://uappexplorer.com/app/navigator.costales The code is here: http://bazaar.launchpad.net/~costales/unav/trunk/view/head:/www/js/geolocation.js It's just a simple HTML5 geolocation code. Even I added a reject control for more that 1 request by 800 microseconds. I think it could be the GPS doing a lot of request by second or the web container is freezing waiting for GPS. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/unav/+bug/1462664/+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 1462977] Re: Thinkpad T440s - Sound muted when docked to docking station
which dock station are you using ? http://support.lenovo.com/us/en/documents/pd014572 -- 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/1462977 Title: Thinkpad T440s - Sound muted when docked to docking station Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi everyone, when I dock my Thinkpad T440s to my docking station, the sound channel for the speakers connected to the docking station audio jack are muted by default. If I run the following command after docking amixer --card 1 sset 'Speaker+LO' 100% the sound starts working. Unfortunatly I have to run this command every time I am docking the system to the docking station. Furthermore there is specific volume slider is not shown in the audio setttings of Unity. So this command could only be a temporary workaround... The internal speakers and the headphones jack of my laptop does not have these problems. It would be really nice if the audio output of the docking stations stays unmuted, when i connect the laptop to the docking station. Maybe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1101386, but the workaround proposed there does not work for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: fabian 2170 F...m pulseaudio /dev/snd/controlC1: fabian 2170 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 8 12:50:20 2015 InstallationDate: Installed on 2015-04-28 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internes Audio - HDA Intel PCH Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQS00600:pvrThinkPadT440s:rvnLENOVO:rn20AQS00600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQS00600 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1462977/+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 1462829] Re: Geis builds are not reproduceable on Debian
** Changed in: geis Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geis in Ubuntu. https://bugs.launchpad.net/bugs/1462829 Title: Geis builds are not reproduceable on Debian Status in Open Input Framework Geis C API: Fix Committed Status in geis package in Ubuntu: Fix Released Status in geis package in Debian: New Bug description: Debian is reporting that packaging builds for Geis are not reproduceable because of some documentation generation timestamp settings. See the linked Debian bug for details. To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/1462829/+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 1463013] Re: geis FTBFS with clang instead of gcc
** Changed in: geis Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geis in Ubuntu. https://bugs.launchpad.net/bugs/1463013 Title: geis FTBFS with clang instead of gcc Status in Open Input Framework Geis C API: Fix Committed Status in geis package in Ubuntu: Fix Released Status in geis package in Debian: Confirmed Bug description: Using the rebuild infrastructure, your package fails to build with clang (instead of gcc). See build logs here: http://clang.debian.net/logs/2014-01-14/geis_2.2.16-1_unstable_clang.log To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/1463013/+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 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
Sorry António, I misread your earlier comment and assigned it to the wrong team again. This is still present in pt_BR.mo: msgstr bigbDigite a linha do APT completa dobr / repositório que quer adicionar como fonte/b/ppA linha do APT inclui o tipo, a localização e os componentes de um repositório,br / por exemplo i\%s\/i./p That can't be right, because the /big is missing. -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in Ubuntu Translations: Fix Committed Status in software-properties package in Ubuntu: In Progress Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The big tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1377742/+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 1424263] Re: Broken dependencies
Unfortunately the bug is still here: sudo apt-get install libgl1-mesa-glx:i386 yields: 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: libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.4) Recommends: libgl1-mesa-dri:i386 (= 7.2) E: Unable to correct problems, you have held broken packages. Nor #6 nor #15 worked here – Steam still complains about missing libGL.so.1 -- 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/1424263 Title: Broken dependencies Status in mesa package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Bug description: I can not install Steam from Steam website because reported package has broken dependencies. This bug affect any user that will install Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on Linux. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri:i386 (not installed) ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.35 Sat Jan 10 21:27:15 PST 2015 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 21 21:40:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84ac] InstallationDate: Installed on 2015-02-20 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Sat Feb 21 17:22:09 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263/+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 1458043] Re: can't connect to adb in emulator and swipe doesn't appear to work
This bug was fixed in the package lxc-android-config 0.225 in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-
phone-overlay
---
lxc-android-config (0.225) vivid; urgency=medium
* Don't disable persist.sys.usb.config when running on the emulator
(LP: #1458043)
-- Ricardo Salveti de Araujo ricardo.salv...@canonical.com Mon, 25
May 2015 19:06:59 -0300
** Changed in: lxc-android-config (Ubuntu RTM)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1458043
Title:
can't connect to adb in emulator and swipe doesn't appear to work
Status in lxc-android-config package in Ubuntu:
Fix Released
Status in lxc-android-config package in Ubuntu RTM:
Fix Released
Bug description:
On vivid with:
ubuntu-emulator 0.21-1+173~ubuntu15.04.1build1
ubuntu-emulator-runtime 20141117-0039-0ubuntu11
I generated an image like so:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed/ubuntu
--arch=i386 devel-proposed.x86
and started with:
$ ubuntu-emulator run --scale=0.75 devel-proposed.x86
then I see a lot of output, but some of it doesn't look right:
[4.944791] init: ureadahead-touch main process (469) terminated with
status 5
[ 12.865870] init: /dev/hw_random not found
[ 12.865870] init: cannot open '/initlogo.rle'
[ 12.887030] init: /dev/hw_random not found
[ 12.945132] init: cannot find '/system/etc/install-recovery.sh', disabling
'flash_recovery'
[ 12.945132] init: cannot find '/system/bin/ubuntuappmanager.disabled',
disabling 'ubuntuappmanager'
[ 12.945132] init: property 'sys.powerctl' doesn't exist while expanding
'${sys.powerctl}'
[ 12.945132] init: powerctl: cannot expand '${sys.powerctl}'
[ 12.945132] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist
while expanding '${sys.sysctl.extra_free_kbytes}'
[ 12.945132] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while
writing to '/proc/sys/vm/extra_free_kbytes'
[ 12.945132] init: cannot find '/sbin/adbd', disabling 'adbd'
[ 12.945132] init: property 'persist.sys.usb.config' doesn't exist while
expanding '${persist.sys.usb.config}'
[ 12.945132] init: cannot expand '${persist.sys.usb.config}' while
assigning to 'sys.usb.config'
* Setting up X socket directories...[ OK
]
/lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
basename: missing operand
Try 'basename --help' for more information.
* Starting virtual private network daemon(s)...
[ 47.445560] systemd-logind[1146]: Failed to start user service: Unknown
unit: user@32011.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1458043/+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 1463430] Re: Clock app crashes when renabling an alarm
** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1463430 Title: Clock app crashes when renabling an alarm Status in QT Ubuntu: New Status in Clock application for Ubuntu devices: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: It seems clock app crashes when reenabling an alarm that just went off. Steps to reproduce the bug: 1. Set an alarm to ring in +1 or +2 minutes 2. Let it ring. 3. Dismiss it 4. Switch back to clock app and then renable that alarm What happens (sometimes) Clock app crashes Out of 10-11 tries, I was able to reproduce the crash only once on my N4 running ubuntu-touch/rc-proposed/ubuntu-developer image #1. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-developer last update: 2015-06-03 16:58:46 version version: 1 version ubuntu: 20150602 version device: 20150210 version custom: 20150508-685-1-11 To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu/+bug/1463430/+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 1463435] [NEW] Copy doesn't actually go to clipboard
Public bug reported: So because of the general limitations in the webbrowser-app, I use firefox as a backup (for videos and downloading files). I occasionally try to select copy, thinking that this will copy the link to a clipboard so that I can give the link to firefox for handling, only to find that there is no paste option in firefox! You must store the copied in the actual clipboard, not in the clipboard that you have created just for this app. This is a big difference for desktop integration. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.23+14.04.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 08:32:42 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-07 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1463435 Title: Copy doesn't actually go to clipboard Status in webbrowser-app package in Ubuntu: New Bug description: So because of the general limitations in the webbrowser-app, I use firefox as a backup (for videos and downloading files). I occasionally try to select copy, thinking that this will copy the link to a clipboard so that I can give the link to firefox for handling, only to find that there is no paste option in firefox! You must store the copied in the actual clipboard, not in the clipboard that you have created just for this app. This is a big difference for desktop integration. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.23+14.04.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 08:32:42 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-07 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1463435/+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 1368647] Re: GPS and location detection not working on Nexus 4
Device: LG Nexus 4 OS: Ubuntu 15.10 r220 dual boot Still no gps at all for any app. I can't make changes as the file system is locked. can anyone confirm the instruction at #11 works? Can anyone say when this will be implemented and released? Can anyone say whether there is any effort to fix GPS on nexus devices out there? if not, please just mark this bug as WONTFIX so i can stop hoping. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1368647 Title: GPS and location detection not working on Nexus 4 Status in location-service package in Ubuntu: Confirmed Bug description: Mako with MultiROM, utopic r239 None of the apps I have tried including Weather, Google maps, OSM Touch and SensorStatus are able to use the phone's GPS. The SensorStatus app actually reports Found supported backend, but finds no position or other GPS data. Location detection on the other hand is doing something, but it is really far off when it comes to determining the actual location of the device. The Weather app suggests my location as Vänsjö, Jämtland, which is about 400 km north of Stockholm where I am at. OSM Touch reports no location available and Google maps Your location could not be determined I don't know if the GPS has to waken up somehow, but it has not shown any form of life for me on Ubuntu Touch, even though it works perfectly fine when booting the phone as Android. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+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 1462977] Re: Thinkpad T440s - Sound muted when docked to docking station
And the speakers are connected to the 1x Stereo/Mic Combo Audio Port mentioned in the device specification of Lenovo. Nothing is connected to the audio port directly at the laptop (that works fine by the way). -- 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/1462977 Title: Thinkpad T440s - Sound muted when docked to docking station Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi everyone, when I dock my Thinkpad T440s to my docking station, the sound channel for the speakers connected to the docking station audio jack are muted by default. If I run the following command after docking amixer --card 1 sset 'Speaker+LO' 100% the sound starts working. Unfortunatly I have to run this command every time I am docking the system to the docking station. Furthermore there is specific volume slider is not shown in the audio setttings of Unity. So this command could only be a temporary workaround... The internal speakers and the headphones jack of my laptop does not have these problems. It would be really nice if the audio output of the docking stations stays unmuted, when i connect the laptop to the docking station. Maybe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1101386, but the workaround proposed there does not work for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: fabian 2170 F...m pulseaudio /dev/snd/controlC1: fabian 2170 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 8 12:50:20 2015 InstallationDate: Installed on 2015-04-28 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internes Audio - HDA Intel PCH Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQS00600:pvrThinkPadT440s:rvnLENOVO:rn20AQS00600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQS00600 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1462977/+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 1413989] Re: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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/1413989 Title: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error- quark, 0). Exiting. Status in lightdm package in Ubuntu: Confirmed Bug description: was logged into /var/log/x-0-greeter.log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4 Uname: Linux 3.19.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Fri Jan 23 14:00:52 2015 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/1413989/+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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the min
I'm affected too, I have 4 HDD in addition with my primary drive (SSD), and I have frequently the bug ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the Files icon on the Launcher again doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Vivid OPM Workspace: New Status in unity package in Ubuntu: Triaged Status in unity source package in Trusty: Confirmed Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the Files icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the Files icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - One way to navigate between windows at this moment is to use the control + tabulation key combination, or to click again on the Files icon so windows are exposed. Otherwise the minimized window Can be restored by clicking on the Volume's launcher icon or scrolling on the Files icon ** SOLUTION ** WORK-AROUND - On the launcher, left click on the Files icon and select the unlock from Launcher option. FIX - The launcher icon for Files to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the Files icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1455408] Re: Recent call not cleared from indicator
seems it did not make the ota ** Changed in: canonical-devices-system-image Milestone: ww22-2015 = ww24-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1455408 Title: Recent call not cleared from indicator Status in the base for Ubuntu mobile products: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Fix Released Status in dialer-app source package in Vivid: Confirmed Status in telephony-service source package in Vivid: Confirmed Bug description: $ system-image-cli -i current build number: 42 device name: arale channel: ubuntu-touch/tangxi/devel-proposed last update: 2015-05-15 04:19:20 version version: 42 version device: 1e1b1cebe8900f5b62bed050a5c23a7765e62600d394cba528169d257e6ab36c version custom: 8274419d06b4da1424e7f7339ff2f8276b38951951d8900e148a4fdfce8fba0d Steps to reproduce: 1.Make a call from another device to this DUT, but don't answer it 2.Hang up the call from remote end 3.Swipe down on the Notification indicator, make sure the Notification indicator opens and shows the missed call 4.Switch to Phone app to check the missed call Launcher/System Settings---Phone--Recent(Swip up from bottom)--Missed 5.Tap on the missed call body 6.The missed call will shown in Dialer 7.Back to check the state of Notifications indicator Expected results: The missed call should not be displayed in Notifications indicator anymore Actual results: The missed call will not disappear in Notifications indicator unless tap on call back or send message or clear all Additional information: This issue could also be reproduced on Krillin r276 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1455408/+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 1463475] [NEW] package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured
Public bug reported: not known ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libffi6:i386 3.1~rc1+r3.0.13-12 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Tue Jun 9 10:45:48 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12:package libffi6:i386 is already installed and configured ErrorMessage: package libffi6:i386 is already installed and configured InstallationDate: Installed on 2015-06-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: libffi Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libffi (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1463475 Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured Status in libffi package in Ubuntu: New Bug description: not known ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libffi6:i386 3.1~rc1+r3.0.13-12 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Tue Jun 9 10:45:48 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libffi6:i386:3.1~rc1+r3.0.13-12:package libffi6:i386 is already installed and configured ErrorMessage: package libffi6:i386 is already installed and configured InstallationDate: Installed on 2015-06-09 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: libffi Title: package libffi6:i386 3.1~rc1+r3.0.13-12 failed to install/upgrade: package libffi6:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1463475/+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 1462489] Re: Allow apps to keep the screen on
The project is this: lp:~unav
I added 'video' 'audio' into the policy_groups.
I added then this both tags
http://doc.qt.io/qt-5/qml-qtmultimedia-audio.html into the QML:
Audio {
}
Video
}
But the screen is setting OFF after 1' :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1462489
Title:
Allow apps to keep the screen on
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Confirmed
Status in ubuntu-system-settings package in Ubuntu:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
Support an interface in QML and HTML to allow an app to keep the
screen on while the app is active. This has come up in several
scenarios, such as an ebook reader, a clock in night mode.
One solution to inhibit the screen blanking:
Add a new dbus rule to the default template
Provide a mediator (unity8) to control this, so it can restore the screen
blanking when the app is not active or has been closed
Prompt the user for confirmation the first time the app accesses it
use the trust store to avoid prompts each time
add to the System settings Other app access panel an entry for Screen or
Display so the setting could be revoked
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1462489/+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 1462664] Re: Geolocation app is freezing in a few mobiles
On Tue, Jun 9, 2015 at 5:33 PM, Sergi Quiles Pérez serg...@gmail.com wrote: It is necessary to have 3G all the time or the app has the ability to work with just the GPS signal (without refresh the map)? Thanks for your feedback Sergi! :) The app needs 3G for set the route maps. Do you have the freeze issue always in the same point? It could be great for debug things. FYI You can set a route with 3G and then, disable the 3G. You'll have a white map (no map) and it can't be recalculate the route. If you'll be in the right way all the time you'll see the blue route line using just GPS. A hug! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1462664 Title: Geolocation app is freezing in a few mobiles Status in uNAV: New Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu RTM: New Bug description: Hi! With the app GPS Navigation a few users have problem with a freeze issue, because of 100% CPU usage or heavy swap usage (I don't know, because I can't reproduce it. For some users, it is working perfect, for other is freezing after a few minutes. You can see here the user reviews: https://uappexplorer.com/app/navigator.costales The code is here: http://bazaar.launchpad.net/~costales/unav/trunk/view/head:/www/js/geolocation.js It's just a simple HTML5 geolocation code. Even I added a reject control for more that 1 request by 800 microseconds. I think it could be the GPS doing a lot of request by second or the web container is freezing waiting for GPS. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/unav/+bug/1462664/+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 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
Having the same issue here as well (although I'm on Arch with 3.16 kernel). Interestingly, on the same computer running Mint (3.13 kernel), there is no issue. With 3.16 kernel, RT61PCI works for some minutes, then disconnects, and unable to reconnect again. Note: both distro's use version 2.3.0 of RT61PCI. dmesg on 3.16 kernel: ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush -- 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/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: vivid Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/01/2000 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: 8363-686A dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd08/01/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363-686A:rvr:cvn:ct3:cvr: dmi.product.name: VT8363 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393744/+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 1461593] Re: No data connection switching from 2G only to 3G
** Changed in: canonical-devices-system-image Milestone: ww24-2015 = ww22-2015 -- 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/1461593 Title: No data connection switching from 2G only to 3G Status in the base for Ubuntu mobile products: In Progress Status in network-manager package in Ubuntu: In Progress Status in network-manager package in Ubuntu RTM: In Progress Bug description: Test case. - Open System Settings. - Go to Cellular. - Switch from 3G to 2G, check that indicator network shows 2G only connection. - Switch from 2G only to 3G. Expected result. - Indicator network shows 3G connection, and user can use data connection. Actual result. - Data connection is lost. Tested in single SIM and dual SIM mode, with two different SIM cards from different operators. current build number: 23 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1461593/+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 1462977] Re: Thinkpad T440s - Sound muted when docked to docking station
I am using the ThinkPad Pro Dock (Type 40A1). That should be this one from the lenovo support page: http://support.lenovo.com/us/en/documents/pd027981 -- 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/1462977 Title: Thinkpad T440s - Sound muted when docked to docking station Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi everyone, when I dock my Thinkpad T440s to my docking station, the sound channel for the speakers connected to the docking station audio jack are muted by default. If I run the following command after docking amixer --card 1 sset 'Speaker+LO' 100% the sound starts working. Unfortunatly I have to run this command every time I am docking the system to the docking station. Furthermore there is specific volume slider is not shown in the audio setttings of Unity. So this command could only be a temporary workaround... The internal speakers and the headphones jack of my laptop does not have these problems. It would be really nice if the audio output of the docking stations stays unmuted, when i connect the laptop to the docking station. Maybe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1101386, but the workaround proposed there does not work for me. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: fabian 2170 F...m pulseaudio /dev/snd/controlC1: fabian 2170 F pulseaudio CurrentDesktop: Unity Date: Mon Jun 8 12:50:20 2015 InstallationDate: Installed on 2015-04-28 (40 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Internes Audio - HDA Intel PCH Symptom_PulseAudioLog: Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel PCH, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQS00600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQS00600:pvrThinkPadT440s:rvnLENOVO:rn20AQS00600:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQS00600 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1462977/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
When I boot using systemd, nothing is logged at all - maybe booting stalls even before rsyslogd is started? If I boot using upstart, the syslog is as follows - note the massive delay before activation of org.freedesktop.UDisks2 which causes the boot process to take quite long - Kubuntu 14.10 had a *much* faster boot process without such a delay. ** Attachment added: syslog while booting using upstart - there are no log entries if I try to boot using systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412154/+files/upstart_syslog.txt -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1413989] Re: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
also seen with Wily i386 ** Tags added: wily -- 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/1413989 Title: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error- quark, 0). Exiting. Status in lightdm package in Ubuntu: Confirmed Bug description: was logged into /var/log/x-0-greeter.log ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4 Uname: Linux 3.19.0-2-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Fri Jan 23 14:00:52 2015 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/1413989/+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 1238346] Re: on bootup wrong keyboard layout is recognized
I'm affected too on Ubuntu 14.04, in fact the keyboard is correctly configured on Azerty (fr) on lightdm, but it switch to Qwerty (en) when the desktop (Unity) starts. I have only the Fr as possible input mapping in the config panel. I must select the Fr icon in the top bar and click on French again to have the correct mapping for the keyboard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1238346 Title: on bootup wrong keyboard layout is recognized Status in One Hundred Papercuts: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: This is a regression. I have two keyboard layouts activated, the Dvorak and the English US. The Dvorak should be the default keyboard. That is the way I have it set up, and it shows up in the task bar on top as En1, which is the Dvorak. However, when I start to type, it starts in QUERTY. ?? To correct this, I go to the task bar (where it shows EN1, or Dvorak), re-select the Dvorak, and then everything is fine. ?? I have another minor problem which should probably go on another bug, but happened at the same time. CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm using. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 10 21:20:39 2013 InstallationDate: Installed on 2013-08-12 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1238346/+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 1463263] [NEW] X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
You have been subscribed to a public bug:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps will
not X11 forward. I was under the impression that Mir would not be in
place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have broken
X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow and
I'm extremely ticked off, I've been trying to troubleshoot it since the
day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a shortcut
created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from another
computer (all 3 were my System76 desktop running from my house)
I have an alias to connect to my server; the command is ssh -p -X
IP and in that, echo $DISPLAY returns a blank line. If I get into the
server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM menu.
Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm' },
{ Terminator, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator' },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any additional information.
** Affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment forwarding mir x11
--
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
https://bugs.launchpad.net/bugs/1463263
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to mir 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 1457321] Re: lxc-stop does not shut down container
I can confirm that vivid containers using the systemd currently in proposed now shut down properly. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1457321 Title: lxc-stop does not shut down container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Released Bug description: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. For the record, in upstart we had /etc/init/shutdown.conf . This is wrong, as it breaks UPS responders like nut (and it also halts instead of poweroff). But we should provide this for containers under systemd. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+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 1457054] Re: journal is broken in unprivileged LXC and nspawn containers
I can confirm that unprivileged vivid containers now start properly with the package from proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1457054 Title: journal is broken in unprivileged LXC and nspawn containers Status in lxc package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Committed Status in systemd source package in Wily: Fix Released Bug description: Test case - - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/ - Boot it. You'll get a lot of errors like [FAILED] Failed to start Journal Service. systemd-journald-audit.socket failed to listen on sockets: Operation not permitted [FAILED] Failed to listen on Journal Audit Socket. - The same happens with systemd-nspawn -b. As a result, the journal isn't working at all, and you have a bunch of failed journal related units. With a fixed systemd package, systemd in the container should realize that it cannot listen to the audit socket (as the kernel doesn't allow that -- the audit subsystem isn't fit for namespaces right now), and sudo journalctl should show the journal and systemd-journald.service should be running. These systemd fixes are sufficient for nspawn, but not completely for unprivileged LXC containers -- there the journal will start working, but systemd-journald-audit.socket will still keep failing (this is less important) REGRESSION POTENTIAL: Very low. This only affects the fallback error code path if binding to the audit socket failed. In that case the journal is currently not working at all. This usually doesn't happen on real iron/VMs (they also always CAP_AUDIT_READ), so there is no practical change there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1457054/+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 1460304] Re: kernel call traces, hard locks ups, nvidia
Should I work more on if is a hardware issue? System locks with kernel 3.16 from Sparky Linux as well. My backup video card Geforce 7900GT has died during testing. Since I've switched CPUs and more errors appeared do you think it could a bad or incompatible motherboard ASUS A8VM? Rule out bad CPUs first? -- 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/1460304 Title: kernel call traces, hard locks ups, nvidia Status in xorg package in Ubuntu: Triaged Bug description: Xorg is locking up not allowing keyboard input, mouse is active but unable to activate any command or menu. full disk checks fsck -c /dev/sdaX are done often, memory tests ok unsure if fault is in xorg or kernel ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 30 11:39:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0370] InstallationDate: Installed on 2015-05-10 (20 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1277): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-power main process (1323) killed by TERM signal init: indicator-application main process (1333) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1277): WARNING **: Failed to load user image: Failed to open file '/home/west/.face': Permission denied init: indicator-power main process (1321) killed by TERM signal init: indicator-application main process (1333) killed by TERM signal MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-generic root=UUID=b2e6ef75-e76d-436c-a4b0-2a40e37828a6 ro verbose SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.name: A8V-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd06/19/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8V-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Sat May 30 10:22:50 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
** Changed in: mir (Ubuntu)
Assignee: (unassigned) = Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
Status in mir package in Ubuntu:
New
Bug description:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps
will not X11 forward. I was under the impression that Mir would not be
in place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have
broken X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow
and I'm extremely ticked off, I've been trying to troubleshoot it
since the day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a
shortcut created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from
another computer (all 3 were my System76 desktop running from my
house)
I have an alias to connect to my server; the command is ssh -p
-X IP and in that, echo $DISPLAY returns a blank line. If I get
into the server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM
menu. Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm' },
{ Terminator, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator' },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any additional information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1463263/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1377742] Re: Window header mistype on selecting best server (portuguese system language, at least)
** Changed in: ubuntu-translations Importance: Undecided = Medium ** Changed in: ubuntu-translations Status: Fix Committed = Triaged ** Changed in: ubuntu-translations Assignee: Ubuntu Portuguese Translators (ubuntu-l10n-pt) = Ubuntu Brazilian Portuguese Translators (ubuntu-l10n-pt-br) -- 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/1377742 Title: Window header mistype on selecting best server (portuguese system language, at least) Status in Ubuntu Translations: Triaged Status in software-properties package in Ubuntu: In Progress Bug description: I believe there is a mistype preventing text from being displayed as the window's header. The big tag was closed incorrectly and so displayed as ordinary text. I do not know if this happens with any other version of Ubuntu except for the Portuguese version. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 23:28:28 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2014-09-21 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1377742/+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 1457201] Re: [Launcher] Add quit app from launcher quicklist
** Branch linked: lp:~lukas-kde/unity8/closeAppsFromQuicklist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1457201 Title: [Launcher] Add quit app from launcher quicklist Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: Add quit app from launcher quicklist, as in unity7 launcher. Always open the spread or switch to the app to close an app on desktop is not very convenient, the feature is quite useful. If the app is hanging it will force close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1457201/+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 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
The following mir-related packages are installed:
surfrock66@sr66-blade:~/.scripts$ dpkg --get-selections | grep -v deinstall |
grep -i mir
libmirclient8:amd64 install
libmircommon3:amd64 install
libmirprotobuf0:amd64 install
mir-client-platform-mesa2:amd64 install
** Package changed: ubuntu = mir (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
Status in mir package in Ubuntu:
New
Bug description:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps
will not X11 forward. I was under the impression that Mir would not be
in place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have
broken X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow
and I'm extremely ticked off, I've been trying to troubleshoot it
since the day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a
shortcut created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from
another computer (all 3 were my System76 desktop running from my
house)
I have an alias to connect to my server; the command is ssh -p
-X IP and in that, echo $DISPLAY returns a blank line. If I get
into the server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM
menu. Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm' },
{ Terminator, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator' },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
Thanks Pat ;) Then, I can't use it, because I have indicator voices and I'm not playing then all the time :( Thanks anyway! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1462489 Title: Allow apps to keep the screen on Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1462489/+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 1463551] [NEW] machine freezes randomly but mouse moves
Public bug reported: I'm not sure what the reason. just collected xorg logs ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Tue Jun 9 23:16:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:198f] InstallationDate: Installed on 2015-05-17 (23 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-38-generic 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: 07/28/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.20 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.55 dmi.chassis.asset.tag: 5CG4455SK4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.20:bd07/28/2014:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3008DD11303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.55:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3008DD11303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Tue Jun 9 19:49:55 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18510 vendor SDC xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1463551 Title: machine freezes randomly but mouse moves Status in xorg package in Ubuntu: New Bug description: I'm not sure what the reason. just collected xorg logs ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Tue Jun 9 23:16:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:198f] InstallationDate: Installed on 2015-05-17 (23 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-38-generic 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: 07/28/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.20 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.55 dmi.chassis.asset.tag: 5CG4455SK4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Touch-packages] [Bug 1463559] [NEW] Incorrect file digest when it is downloaded through webbrowser-app with touch
Public bug reported: I download an image from a webpage and the sha1 digest is not the same than the original. It is happening at least in the krilling (touch). I tested this scenario with different images and always it is happening the same. Steps to reproduce: 1. Go to lillypilly.canonical.com/~platform-qa/page3.html 2. Touch in the ubuntu image 3. Select Save image 4. Select to open with the Galery 5. Once it is downloaded, press open 6. The file is in ~/Pictures/ubuntu.jpg The file sha1 digest is 7cad64e34de2eebe73b49756b09a50a4a1948c7a The original sha1 digest is 429cbd692c4abd3e5c785edf5dcf0993d21076b1 If you download the image either with chrome or firefox, the obtained digest is the correct one. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1463559 Title: Incorrect file digest when it is downloaded through webbrowser-app with touch Status in webbrowser-app package in Ubuntu: New Bug description: I download an image from a webpage and the sha1 digest is not the same than the original. It is happening at least in the krilling (touch). I tested this scenario with different images and always it is happening the same. Steps to reproduce: 1. Go to lillypilly.canonical.com/~platform-qa/page3.html 2. Touch in the ubuntu image 3. Select Save image 4. Select to open with the Galery 5. Once it is downloaded, press open 6. The file is in ~/Pictures/ubuntu.jpg The file sha1 digest is 7cad64e34de2eebe73b49756b09a50a4a1948c7a The original sha1 digest is 429cbd692c4abd3e5c785edf5dcf0993d21076b1 If you download the image either with chrome or firefox, the obtained digest is the correct one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1463559/+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 664785] Re: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had sound in 10.04, not 10.10
*** This bug is a duplicate of bug 662299 ***
https://bugs.launchpad.net/bugs/662299
Bug #662299 includes several problems with similar symptoms and the same
workaround (booting with pci=use_crs).
Booting with pci=use_crs may be a workaround for this bug as well. If
it is, please attach a complete dmesg log here so we can make the kernel
work even without the pci=use_crs option.
--
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/664785
Title:
VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) had
sound in 10.04, not 10.10
Status in alsa-driver package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
New
Bug description:
Will test the upstream kernel...
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 1: Adapter [Nokia Wireless Audio Adapter], device 0: USB Audio [USB
Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 2: CX8811 [Conexant CX8811], device 0: CX88 Digital [CX88 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: james 1668 F pulseaudio
/dev/snd/controlC1: james 1668 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card1.Amixer.info:
Card hw:1 'Adapter'/'Nokia Wireless Audio Adapter at usb-:00:10.4-3.1.3,
full speed'
Mixer name : 'USB Mixer'
Components : 'USB0a12:1004'
Controls : 0
Simple ctrls : 0
Card1.Amixer.values:
Card2.Amixer.info:
Card hw:2 'CX8811'/'Conexant CX8811 at 0xf900'
Mixer name : 'CX88'
Components : ''
Controls : 3
Simple ctrls : 2
Date: Thu Oct 21 22:29:02 2010
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=91b0fc3a-1497-48c1-92a5-afffe37f48f5
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
root=UUID=21480595-8b0c-49d3-903b-05a172d6499a ro quiet splash
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
SourcePackage: linux
dmi.bios.date: 10/30/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0304
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2V-MX SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd10/30/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2V-MXSE:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/664785/+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 682185] Re: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
*** This bug is a duplicate of bug 662299 *** https://bugs.launchpad.net/bugs/662299 Bug #662299 includes several problems with similar symptoms and the same workaround (booting with pci=use_crs). Booting with pci=use_crs may be a workaround for this bug as well. If it is, please attach a complete dmesg log here so we can make the kernel work even without the pci=use_crs option. -- 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/682185 Title: Soundcard not detected - VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) Status in ALSA driver: New Status in alsa-driver package in Ubuntu: Incomplete Bug description: lspci: 80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) Kernal is supposed to run: snd-hda-intel o But I can't find it... ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-11-27 18:38 seq crw-rw+ 1 root audio 116, 2 2010-11-27 18:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: aplay: device_list:235: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:235: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 27 18:46:15 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Soundcard not detected dmi.bios.date: 06/27/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V1.4 dmi.board.name: MS-7253 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.4:bd06/27/2007:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr: dmi.product.name: MS-7253 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/682185/+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 931912] Re: [Dell Latitude E6510] PCI/internal sound card not detected, unless pci=use_crs is specified
Manuel, does this problem still occur? I can't see what the problem is in your dmesg logs. Your logs contain 'PCI: Using host bridge windows from ACPI; if necessary, use pci=nocrs and report a bug', booting with pci=use_crs shouldn't make a difference on your machine. If this is still a problem, can you attach the complete dmesg logs both with and without pci=use_crs? Thanks! -- 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/931912 Title: [Dell Latitude E6510] PCI/internal sound card not detected, unless pci=use_crs is specified Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with 12.04 Precise Pangolin x86_64 platform. After update the system to 14th February 2012, at 9 AM Europe/Spain hour, all is working fine except the sound system. No alsa modules is loaded, no sound. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.24+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 AlsaDevices: total 0 crw-rw---T+ 1 root audio 116, 1 feb 14 08:53 seq crw-rw---T+ 1 root audio 116, 33 feb 14 08:53 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:242: no soundcards found... ApportVersion: 1.91-0ubuntu1 Architecture: amd64 ArecordDevices: arecord: device_list:242: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Feb 14 09:02:52 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.1) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931912/+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 1463189] Re: SIM unlocking doesn't work after reboot in flight-mode
*** This bug is a duplicate of bug 1460987 *** https://bugs.launchpad.net/bugs/1460987 ** This bug has been marked a duplicate of bug 1460987 Cannot unlock SIM after booting in flight mode -- 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/1463189 Title: SIM unlocking doesn't work after reboot in flight-mode Status in network-manager package in Ubuntu: New Bug description: When an aquaris E4.5 device is booting with activated flight-mode the SIM can't be unlocked. Steps to reproduce: 1. Activate flight-mode. 2. Reboot. 3. The device boots up with activated flight-mode. 4. Disable flight mode. 5. Open the indicator Network and try to push the button Unlock SIM. 6. Nothing happens. Note 1: In order to unlock SIM the device has to be rebooted again with disabled flight-mode. Note 2: If the flight-mode is disabled without a previous reboot the button Unlock SIM is working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1463189/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
I have a very similar issue. Upstart works but systemd does not. Lucs encrypted logical volume on a work computer. It has worked flawless with boot for many versions of Ubuntu (even before upstart I think). I can produce the syslog with two boots tomorrow. Also have taken a picture of the actual error message during boot with systemd, which is attached. Upstart presents the password prompt, systemd does not. ** Attachment added: Picture of output during boot with systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412269/+files/20150609_175942.jpg -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 839208] Re: PCI/internal sound card not detected: Soundblaster Audigy SE
Hi timmy, pci=use_crs shouldn't make any difference on your system, because it was already automatically enabled even without pci=use_crs. If you still have an issue with sound or xgifb, please attach a complete dmesg log. -- 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/839208 Title: PCI/internal sound card not detected: Soundblaster Audigy SE Status in alsa-driver package in Ubuntu: New Bug description: tried following http://ubuntuforums.org/showthread.php?t=205449. no luck :( ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. Compiled on Aug 25 2011 for kernel 2.6.38-11-generic (SMP). Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D2', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Sep 1 21:16:22 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0815 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B-X series dmi.board.vendor: ASUSTeK Computer INC. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0815:bd06/27/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnP8B-Xseries:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/839208/+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 662299] Re: Soundcard not detected (workaround: add pci=use_crs to GRUB)
pci=use_crs is a workaround but not a fix. If anybody who has this problem can attach a complete dmesg log, we should be able to fix the kernel so it works without having to boot with pci=use_crs. -- 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/662299 Title: Soundcard not detected (workaround: add pci=use_crs to GRUB) Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I was using Ubuntu 10.04 64 bit with sound enabled. After I updated to Ubuntu 10.10 64 bit its saying no sound cards detected. Report generated by alsa-info.sh : http://www.alsa- project.org/db/?f=6fd7c2b5363fb860fbfdf2fcbce5af440562f0a1 Name of my Sound Card (onboard) anish@logika:~/Downloads$ sudo lshw -c sound [sudo] password for anish: *-multimedia description: Audio device product: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) vendor: VIA Technologies, Inc. physical id: 1 bus info: pci@:80:01.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=HDA Intel latency=0 resources: iomemory:fd0-fcf irq:17 memory:fd-fd3fff anish@logika:~/Downloads$ lspci | grep -i audio 80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-17 23:01 seq crw-rw+ 1 root audio 116, 2 2010-10-17 23:01 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: aplay: device_list:235: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:235: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Oct 17 23:36:06 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Soundcard not detected dmi.bios.date: 05/10/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.11 dmi.board.name: 0A88h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA74206SB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.11:bd05/10/2007:svnHewlett-Packard:pnHPdx2255MT(RL028AV):pvr:rvnBoardManufacturer:rn0A88h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2255 MT(RL028AV) dmi.sys.vendor: Hewlett-Packard --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-19 22:29 seq crw-rw+ 1 root audio 116, 2 2010-10-19 22:29 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Oct 17 2010 for kernel 2.6.35-22-generic (SMP). AplayDevices: aplay: device_list:235: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:235: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 10.10 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) Package: alsa-driver (not installed) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Tags: maverick Uname: Linux 2.6.35-22-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/10/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.11 dmi.board.name: 0A88h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA74206SB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.11:bd05/10/2007:svnHewlett-Packard:pnHPdx2255MT(RL028AV):pvr:rvnBoardManufacturer:rn0A88h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2255 MT(RL028AV) dmi.sys.vendor: Hewlett-Packard --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-20 22:10 seq crw-rw+ 1 root audio 116, 2 2010-10-20 22:10 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Oct 20 2010 for kernel 2.6.35-22-generic (SMP). AplayDevices: aplay: device_list:235: no soundcards found... Architecture: amd64 ArecordDevices:
