[Dx-packages] [Bug 1281058] Re: The system shutdowns when multiple accounts are open
** Changed in: unity (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
** Changed in: oem-priority Status: New => Fix Released ** Changed in: oem-priority/trusty Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Committed Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout notification prompts not scaled after toggling UI scale Edit
** Changed in: unity (Ubuntu) Assignee: (unassigned) => Stephen M. Webb (bregma) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout notification prompts not scaled after toggling UI scale Edit Status in OEM Priority Project: New Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings > Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Stephen, can you assign someone to this bug, please? We will need it fixed in Trusty at least. ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Stephen M. Webb (bregma) ** Changed in: unity (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: New Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1307701] Re: Unity does not get touch events when SDK apps running
** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority/trusty Importance: Undecided => Critical ** Changed in: oem-priority/trusty Status: Confirmed => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/trusty Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit
** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit Status in OEM Priority Project: Triaged Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings > Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit Status in OEM Priority Project: Triaged Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: New Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings > Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 892370] Re: The time zone for China should default to Beijing not Shanghai (when offline)
** Changed in: oem-priority Status: In Progress => Won't Fix ** Changed in: oem-priority/raring Status: In Progress => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/892370 Title: The time zone for China should default to Beijing not Shanghai (when offline) Status in The Date and Time Indicator: New Status in OEM Priority Project: Won't Fix Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project quantal series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in Ubuntu Kylin: New Status in “indicator-datetime” package in Ubuntu: In Progress Status in “libtimezonemap” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Confirmed Status in “indicator-datetime” source package in Quantal: Won't Fix Status in “libtimezonemap” source package in Quantal: Won't Fix Status in “ubiquity” source package in Quantal: Won't Fix Status in “indicator-datetime” source package in Raring: Won't Fix Status in “libtimezonemap” source package in Raring: Fix Released Status in “ubiquity” source package in Raring: Won't Fix Status in “indicator-datetime” source package in Saucy: Confirmed Status in “libtimezonemap” source package in Saucy: Fix Released Status in “ubiquity” source package in Saucy: Confirmed Bug description: When installing Ubuntu and selecting Simplified Chinese as the default language, the default timezone should point to Beijing instead of Shanghai. Everything in China is referenced to Beijing time. In mainland China this standard time is called Beijing Time (北京时间) domestically but it is commonly referred to as China Standard Time (CST) internationally. This seems to have come up a lot in past bugs: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/228554 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/517621 Steps to recreate: 1) Install Ubuntu and select Simplified Chinese for the language. Actual Results: At the timezone page, the default city is Shanghai. Expected Results: Most Chinese users prefer it be set to Beijing. It looks as if the upstream tz database needs to be updated for Beijing for starters, as Beijing is not listed in there. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: tzdata 2011n-0ubuntu0.11.10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 18 15:26:03 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/892370/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
** Also affects: indicator-session (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-greeter (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: New Status in “systemd” source package in Trusty: New Status in “unity” source package in Trusty: New Status in “unity-greeter” source package in Trusty: New Bug description: [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
** Changed in: unity-greeter (Ubuntu Trusty) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: New Status in “systemd” source package in Trusty: New Status in “unity” source package in Trusty: New Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1218810] Re: video switch hot key will return "super key and p" and no response to switch video mode
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1218810
Title:
video switch hot key will return "super key and p" and no response to
switch video mode
Status in “linux” package in Ubuntu:
Confirmed
Status in “unity” package in Ubuntu:
New
Status in “linux” source package in Precise:
New
Status in “unity” source package in Precise:
New
Status in “linux” source package in Trusty:
Fix Released
Status in “unity” source package in Trusty:
Fix Released
Bug description:
CID 201209-11735
For some machines, for example, HP laptop "HP 1000" has a hot key on F4 to
perform the shorcut "super + p" to switch video modes.
Use command "sudo showkey -k" to capture the key code of the hot key you will
see the key code of "super key" and "p"
This key combination is expected to change the video mode.
platfrom: HP laptop "HP 1000"
image: 12.04.3
Steps to reproduce:
1. open an terminal,
2. plugin an external monitor
3. press the video switch hotkey, for "HP 1000" it is the F4 key
Expected result:
1. Video mode is changed by the hotkey
2. no character is printed on terminal
Actual result
1. Video mode is not changed.
2. a "p" will be printed on the terminal screen
The other information:
1. A similar bug was reported on LP:#539477 before.
2. The hotkey in 13.04 works
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Fri Aug 30 17:34:56 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1675 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x6360 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,103c1855,00100202
HDA:80862806,80860101,0010'
Controls : 27
Simple ctrls : 10
CurrentDmesg:
[ 45.884915] ISO 9660 Extensions: RRIP_1991A
[ 60.442781] audit_printk_skb: 3 callbacks suppressed
[ 60.442785] type=1400 audit(1378093422.964:31): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5"
name="/usr/share/gvfs/remote-volume-monitors/" pid=1849 comm="mission-control"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 65.385488] r8169 :0e:00.0 eth0: link up
[ 65.385510] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=932733cb-db60-4153-8565-3e3ccb1a6f6d
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
Lsusb:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
MachineType: Hewlett-Packard HP 1000 Notebook PC
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 radeondrmfb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=770667e1-92a4-4f2e-a434-b9998d55cb30 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8
[Dx-packages] [Bug 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Changed in: oem-priority/trusty Status: Triaged => Fix Committed ** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: Fix Committed Status in OEM Priority Project trusty series: Fix Committed Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Changed in: oem-priority/trusty Status: Fix Committed => Fix Released ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit
** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority Status: Triaged => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings > Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1331037] [NEW] Touchscreens: The mouse cursor disappears when touching the screen
Public bug reported: Single touch does cursor emulation, so I would expect that when I touch the touchscreen, the cursor jumps to the touch position. Instead of doing that, the cursor disappears until I use the mouse again. Touch events work correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jun 17 17:03:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331037 Title: Touchscreens: The mouse cursor disappears when touching the screen Status in OEM Priority Project: New Status in “unity” package in Ubuntu: New Bug description: Single touch does cursor emulation, so I would expect that when I touch the touchscreen, the cursor jumps to the touch position. Instead of doing that, the cursor disappears until I use the mouse again. Touch events work correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jun 17 17:03:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1331037/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1331037] Re: Touchscreens: The mouse cursor disappears when touching the screen
** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Changed in: oem-priority Status: New => Confirmed ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331037 Title: Touchscreens: The mouse cursor disappears when touching the screen Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: New Bug description: Single touch does cursor emulation, so I would expect that when I touch the touchscreen, the cursor jumps to the touch position. Instead of doing that, the cursor disappears until I use the mouse again. Touch events work correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jun 17 17:03:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1331037/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
** Changed in: oem-priority Assignee: (unassigned) => Ara Pulido (apulido) ** Changed in: oem-priority/precise Assignee: (unassigned) => Ara Pulido (apulido) -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “notify-osd” package in Ubuntu: Confirmed Bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send "first title" "first subtitle" -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send "second title" "second subtitle" -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION="Ubuntu 9.04" Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers Original-Maintainer: Andre Filipe de Assuncao e Brito Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
** Also affects: notify-osd (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “notify-osd” package in Ubuntu: Confirmed Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the "x-canonical-private- synchronous" to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the "x-canonical-private- synchronous" interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 "wireless" "disable" -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 "bluetooth" "enable" -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect "x -canonical-private-synchronous" interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send "first title" "first subtitle" -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send "second title" "second subtitle" -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION="Ubuntu 9.04" Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers Original-Maintainer: Andre Filipe de Assuncao e Brito Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1218810] Re: video switch hot key will return "super key and p" and no response to switch video mode
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1218810
Title:
video switch hot key will return "super key and p" and no response to
switch video mode
Status in “linux” package in Ubuntu:
Confirmed
Status in “unity” package in Ubuntu:
New
Bug description:
CID 201209-11735
For some machines, for example, HP laptop "HP 1000" has a hot key on F4 to
perform the shorcut "super + p" to switch video modes.
Use command "sudo showkey -k" to capture the key code of the hot key you will
see the key code of "super key" and "p"
This key combination is expected to change the video mode.
platfrom: HP laptop "HP 1000"
image: 12.04.3
Steps to reproduce:
1. open an terminal,
2. plugin an external monitor
3. press the video switch hotkey, for "HP 1000" it is the F4 key
Expected result:
1. Video mode is changed by the hotkey
2. no character is printed on terminal
Actual result
1. Video mode is not changed.
2. a "p" will be printed on the terminal screen
The other information:
1. A similar bug was reported on LP:#539477 before.
2. The hotkey in 13.04 works
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified:
boot/vmlinuz-3.8.0-29-generic]
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Fri Aug 30 17:34:56 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1675 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x6360 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,103c1855,00100202
HDA:80862806,80860101,0010'
Controls : 27
Simple ctrls : 10
CurrentDmesg:
[ 45.884915] ISO 9660 Extensions: RRIP_1991A
[ 60.442781] audit_printk_skb: 3 callbacks suppressed
[ 60.442785] type=1400 audit(1378093422.964:31): apparmor="DENIED"
operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5"
name="/usr/share/gvfs/remote-volume-monitors/" pid=1849 comm="mission-control"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 65.385488] r8169 :0e:00.0 eth0: link up
[ 65.385510] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=932733cb-db60-4153-8565-3e3ccb1a6f6d
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
Lsusb:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 05c8:0223 Cheng Uei Precision Industry Co., Ltd
(Foxlink)
MachineType: Hewlett-Packard HP 1000 Notebook PC
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 radeondrmfb
1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=770667e1-92a4-4f2e-a434-b9998d55cb30 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/25/2012
dmi.bios.vendor: Insyde
dmi.bios.version: B.50
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1855
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.22
dmi.chassis.asset.tag: Classis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Cha
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
mpt's comment (https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/404658/comments/2) says that "None of the synchronous notifications use text", which is true for current notifications, but looking at the specification (https://wiki.ubuntu.com/NotifyOSD) I haven't found a requirements that Synchronous notification should never have text. In which case, we need to define a behaviour for sync notifications that do. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “notify-osd” package in Ubuntu: Confirmed Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the "x-canonical-private- synchronous" to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the "x-canonical-private- synchronous" interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 "wireless" "disable" -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 "bluetooth" "enable" -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect "x -canonical-private-synchronous" interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send "first title" "first subtitle" -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send "second title" "second subtitle" -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION="Ubuntu 9.04" Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers Original-Maintainer: Andre Filipe de Assuncao e Brito Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
Mirco, these are the icons related to bug https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658 Those were created by the design team. Can we get them into Precise, please? ** Changed in: notify-osd-icons (Ubuntu) Assignee: (unassigned) => Mirco Müller (macslow) ** Also affects: notify-osd-icons (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Ara Pulido (apulido) -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons Status in OEM Priority Project: New Status in “notify-osd-icons” package in Ubuntu: New Status in “notify-osd-icons” source package in Precise: New Bug description: 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons Status in OEM Priority Project: In Progress Status in “notify-osd-icons” package in Ubuntu: Fix Released Status in “notify-osd-icons” source package in Precise: New Bug description: 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in Notify OSD: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “notify-osd” package in Ubuntu: Fix Released Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the "x-canonical-private- synchronous" to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the "x-canonical-private- synchronous" interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 "wireless" "disable" -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 "bluetooth" "enable" -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect "x -canonical-private-synchronous" interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send "first title" "first subtitle" -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send "second title" "second subtitle" -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION="Ubuntu 9.04" Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers Original-Maintainer: Andre Filipe de Assuncao e Brito Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
** Changed in: oem-priority Status: In Progress => Fix Released ** Changed in: oem-priority/precise Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in Notify OSD: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “notify-osd” package in Ubuntu: Fix Released Status in “notify-osd” source package in Precise: Fix Released Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the "x-canonical-private- synchronous" to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the "x-canonical-private- synchronous" interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 "wireless" "disable" -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 "bluetooth" "enable" -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect "x -canonical-private-synchronous" interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send "first title" "first subtitle" -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send "second title" "second subtitle" -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION="Ubuntu 9.04" Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers Original-Maintainer: Andre Filipe de Assuncao e Brito Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libnotify1 (>= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd-icons in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons Status in OEM Priority Project: Fix Released Status in “notify-osd-icons” package in Ubuntu: Fix Released Status in “notify-osd-icons” source package in Precise: Fix Released Bug description: 12.04 Precise SRU info: [Impact] The package provide new notify-osd-icons for Radio enable/disable and Display switch. This is related to https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/404658 to be used in OEM projects. [Test Case] The package should be install/upgrade correctly. [Regression Potential] No known risk right now. [Other Info] 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access
** Changed in: unity/7.2 Status: Fix Committed => Fix Released ** Changed in: oem-priority Status: In Progress => Fix Released ** Changed in: oem-priority/trusty Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [ Impact ] Using a display scaling factor of > 1.0 the 'large text' setting is sometimes enabled automatically on session start, doubling the scaling factor. [ Test Case ] (1) Using the System Settings > Displays > Scale for menu and title bars slider, set the scaling to a value > 1 (for example, 1.88). (2) Log out and in several times. Since this problem occurs as a result of a race condition somewhere, it is not reliably reproducable. [ Regression Potential ] Any code change to the Unity desktop shell could introduce a new crash or lockup. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time without demonstrating regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1420630] Re: indicator-sound menu icon disappeared after volume down to zero
I cannot reproduce this on stock Ubuntu Have you tried reproducing this on stock Ubuntu? ** Changed in: oem-priority/trusty Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1420630 Title: indicator-sound menu icon disappeared after volume down to zero Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Incomplete Status in indicator-sound package in Ubuntu: Triaged Status in indicator-sound source package in Trusty: New Bug description: On the HP commercial notebooks, there're function keys to control volume. The menu volume icon will be disappeared if we volume down (with key combination: Fn+F6, you can also emulate the keys with "xdotool key XF86AudioLowerVolume") to zero then logout and back in. But if we just zero down volume(with the single volume on/off button), then logout and back in, the volume icon is still there. This issue is fixed with installing indicator- sound_12.10.2+14.10.20141010-0ubuntu1(Utopic) Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Feb 11 14:18:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-trusty-amd64-20150114-3 InstallationDate: Installed on 2015-01-29 (13 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150114-08:50 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1420630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Changed in: oem-priority Status: New => Invalid ** Changed in: oem-priority/trusty Status: New => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in OEM Priority Project: Invalid Status in OEM Priority Project trusty series: Invalid Status in compiz package in Ubuntu: Confirmed Status in compiz-plugins-main package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Changed in: oem-priority/precise Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1066157 Title: dash +orca does not speak the names of application icons Status in OEM Priority Project: Fix Released Status in Unity: Fix Released Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Screen reader support for dynamic content in the Dash is enabled. [Test Case] (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader) (2) Press Super + A to bring up the Applications lens of the Dash (3) Navigate displayed content (4) Choose an application for preview (5) Press Esc until the Dash is closed, repeat steps 2 to 4 You should hear the application description and preview description. [Regression Potential] Some new code deals with processing pointers: the usual problem potential of dealing with pointers in C code applies. [Other Info] This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in public use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 892370] Re: The time zone for China should default to Beijing not Shanghai (when offline)
** Changed in: oem-priority Assignee: James M. Leddy (jm-leddy) => Ara Pulido (apulido) ** Changed in: oem-priority/quantal Assignee: James M. Leddy (jm-leddy) => (unassigned) ** Changed in: oem-priority/raring Assignee: James M. Leddy (jm-leddy) => (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/892370 Title: The time zone for China should default to Beijing not Shanghai (when offline) Status in The Date and Time Indicator: New Status in OEM Priority Project: In Progress Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project quantal series: Won't Fix Status in OEM Priority Project raring series: In Progress Status in Ubuntu Kylin: New Status in “indicator-datetime” package in Ubuntu: In Progress Status in “libtimezonemap” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Confirmed Status in “indicator-datetime” source package in Quantal: Won't Fix Status in “libtimezonemap” source package in Quantal: Won't Fix Status in “ubiquity” source package in Quantal: Won't Fix Status in “indicator-datetime” source package in Raring: Won't Fix Status in “libtimezonemap” source package in Raring: Fix Released Status in “ubiquity” source package in Raring: Won't Fix Status in “indicator-datetime” source package in Saucy: Confirmed Status in “libtimezonemap” source package in Saucy: Fix Released Status in “ubiquity” source package in Saucy: Confirmed Bug description: When installing Ubuntu and selecting Simplified Chinese as the default language, the default timezone should point to Beijing instead of Shanghai. Everything in China is referenced to Beijing time. In mainland China this standard time is called Beijing Time (北京时间) domestically but it is commonly referred to as China Standard Time (CST) internationally. This seems to have come up a lot in past bugs: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/228554 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/517621 Steps to recreate: 1) Install Ubuntu and select Simplified Chinese for the language. Actual Results: At the timezone page, the default city is Shanghai. Expected Results: Most Chinese users prefer it be set to Beijing. It looks as if the upstream tz database needs to be updated for Beijing for starters, as Beijing is not listed in there. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: tzdata 2011n-0ubuntu0.11.10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 18 15:26:03 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/892370/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] [NEW] The system shutdowns when multiple accounts are open
Public bug reported: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 11:49:48 2014 InstallationDate: Installed on 2013-06-17 (244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1281058 Title: The system shutdowns when multiple accounts are open Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 11:49:48 2014 InstallationDate: Installed on 2013-06-17 (244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
Marking it as Fix released in the OEM priority project ** Changed in: unity (Ubuntu Precise) Status: Confirmed => Won't Fix ** Changed in: unity (Ubuntu) Status: Triaged => Fix Released ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Fix Released Status in Unity 5.0 series: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Won't Fix Bug description: To Reproduce (in a system with a touch screen) 1. Boot the system and don't touch the screen 2. Set the Launcher to autohide 3. Move the cursor to the left (using the touchpad or an external mouse) 4. The Launcher is revealed successfully 5. Wait until the launcher hides again 6. Now, touch the screen for the first time (no matter where you touch the screen) 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher Expected result: Launcher is revealed Actual result: Launcher cannot be revealed. Additional information: 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
Marking it as Won't Fix in OEM priority project as the behaviour in Trusty is completely different ** Changed in: oem-priority/precise Status: In Progress => Won't Fix ** Changed in: oem-priority Status: In Progress => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Fix Released Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in “gnome-session” package in Ubuntu: Triaged Status in “indicator-session” package in Ubuntu: Triaged Status in “policykit” package in Ubuntu: Triaged Bug description: [Impact] * A user tries to shut down their machine. They get confused because nothing happens when they click shutdown. * If someone else is logged in, they will have to ask that person to "Switch User" to log in and log out * If someone else is logged in and you don't know the password of the account, you can't shut down [Test Case] * Have two login accounts * Log both people in, via power cog->lock screen->switch user * lock the screen on current account, via power cog->lock screen * get back to lightdm via switch user * log in to an already logged in account, and try to power off the machine [Regression Potential] * It wasn't possible to shutdown at all before * I can't see a case for a regression, since it never worked to begin with [Original Report] Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say "not allowed" or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown.s To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] Re: The system shutdowns when multiple accounts are open
** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority/trusty Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1395709] [NEW] Silence mode goes unchecked after 1 second
Public bug reported: Using the phone in version 9, rtm English channel, but configured in Spanish. Steps to reproduce: 1) Go to system-settings/sound and enable silent mode 2) Reboot the phone 3) Unlock the SIM 4) Open the Sound Indicator and leave it open 5) Toggle Silence mode 6) Leave the indicator open and wait. Expected results * Silent mode is already checked on boot (bug 1391164) * Silence mode stays checked Actual results * Silence mode goes back unchecked after 0.5 seconds. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1395709 Title: Silence mode goes unchecked after 1 second Status in “indicator-sound” package in Ubuntu: New Bug description: Using the phone in version 9, rtm English channel, but configured in Spanish. Steps to reproduce: 1) Go to system-settings/sound and enable silent mode 2) Reboot the phone 3) Unlock the SIM 4) Open the Sound Indicator and leave it open 5) Toggle Silence mode 6) Leave the indicator open and wait. Expected results * Silent mode is already checked on boot (bug 1391164) * Silence mode stays checked Actual results * Silence mode goes back unchecked after 0.5 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395709/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354498] Re: Switcher Icons emblem (count) is too small
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354498 Title: Switcher Icons emblem (count) is too small Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: New Bug description: [ Impact] The emblem size does not change as the icon size is adjusted. [ Test Case ] (1) Use the System Settings > Displays > Scale for menus and title bars slider to adjust the Swicther icon size. (2) Observe the size of the badge. It should scale with the icon size. [ Regression Potential Any code change to the Unity desktop shell has the potential to introduce new crashers or lockers. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1354498/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1066157 Title: dash +orca does not speak the names of application icons Status in OEM Priority Project: New Status in Unity: Confirmed Status in Unity 5.0 series: New Status in Unity 6.0 series: New Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Triaged Bug description: using orca and navigating around the dash with the keyboard I hear the names of videos, shopping results, files and folders, application suggestions from the software centre, but not the very most important thing in the dash - applications installed that I might want to run. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working
** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: Fix Committed Status in indicator-bluetooth package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Released Bug description: indicator * Impact The bluetooth indicator includes a non working "browse files..." items * Test case connect/pair a phone which does obex, open the bluetooth indicator and select the device, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- ucc * Impact The bluetooth settings include a non working "browse files..." items * Test case connect/pair a phone which does obex, open settings->bluetooth, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in indicator-bluetooth source package in Xenial: Fix Released Status in unity-control-center source package in Xenial: Fix Released Bug description: indicator * Impact The bluetooth indicator includes a non working "browse files..." items * Test case connect/pair a phone which does obex, open the bluetooth indicator and select the device, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- ucc * Impact The bluetooth settings include a non working "browse files..." items * Test case connect/pair a phone which does obex, open settings->bluetooth, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
** Changed in: oem-priority Status: In Progress => Fix Released ** Changed in: oem-priority/trusty Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: Confirmed Status in “systemd” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Fix Released Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Other users logged into a system may loose work if another user shuts down/reboots a system. Data loss is not a Good Thing. [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be "Other users are currently logged in to this computer, shutting down now will also close these other sessions" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit
** Changed in: oem-priority/trusty Status: New => Fix Released ** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings > Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled [Inpact] When Caps lock was active the icon did not render a tooltip if you moused over the icon. This can be consfusing if the user has no clue what the icon means. [Test case] 1) Go to System Settings -> Display 2) Change the DPI scale to a noticable size. 3) Then select Shutdown to bring up the Dialog. Expected Result: The shutdown dialog scaled correctly. [Regression potential] Low. Worse case we just dont scale, the changes are pretty isolated to the number changing game. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1331037] Re: Touchscreens: The mouse cursor disappears when touching the screen
Marking as Invalid, as this is the intended behaviour. ** Changed in: unity (Ubuntu Trusty) Status: Confirmed => Invalid ** Changed in: oem-priority Status: Confirmed => Invalid ** Changed in: unity Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331037 Title: Touchscreens: The mouse cursor disappears when touching the screen Status in OEM Priority Project: Invalid Status in OEM Priority Project trusty series: New Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Status in “unity” source package in Trusty: Invalid Bug description: Single touch does cursor emulation, so I would expect that when I touch the touchscreen, the cursor jumps to the touch position. Instead of doing that, the cursor disappears until I use the mouse again. Touch events work correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jun 17 17:03:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1331037/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1316734] Re: Scaling factors for high DPI screens are sometimes applied twice
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Importance: Undecided => High ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1316734 Title: Scaling factors for high DPI screens are sometimes applied twice Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: New Bug description: I have a high DPI screen, and thus configured Unity to scale everything by a factor of 1.62 (Under Settings -> Display). Sometimes after logging in the text is suddenly much larger than before, and this change persists even after reboot. I was able to get back normal font sizes by modifying text scaling in unity tweak. I'd have to look at this again the next time this happens, but if I understand this correctly then sometimes the scaling factor is re- applied to the text scaling in cases where it was already applied before, thus scaling the text by 1.62*1.62 instead of only 1.62 as it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1316734/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: New Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332947/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1332947] Re: HDPI: unity randomly turns on large text in universal access
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Tim, is this still happening? I cannot reproduce it in Trusty ** Changed in: oem-priority Status: Triaged => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1420630] Re: indicator-sound menu icon disappeared after volume down to zero
** Changed in: indicator-sound (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1420630 Title: indicator-sound menu icon disappeared after volume down to zero Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Incomplete Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound source package in Trusty: New Bug description: On the HP commercial notebooks, there're function keys to control volume. The menu volume icon will be disappeared if we volume down (with key combination: Fn+F6, you can also emulate the keys with "xdotool key XF86AudioLowerVolume") to zero then logout and back in. But if we just zero down volume(with the single volume on/off button), then logout and back in, the volume icon is still there. This issue is fixed with installing indicator- sound_12.10.2+14.10.20141010-0ubuntu1(Utopic) Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Feb 11 14:18:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-trusty-amd64-20150114-3 InstallationDate: Installed on 2015-01-29 (13 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150114-08:50 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1420630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1420630] Re: indicator-sound menu icon disappeared after volume down to zero
** Changed in: oem-priority Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1420630 Title: indicator-sound menu icon disappeared after volume down to zero Status in OEM Priority Project: Incomplete Status in OEM Priority Project trusty series: Incomplete Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound source package in Trusty: New Bug description: On the HP commercial notebooks, there're function keys to control volume. The menu volume icon will be disappeared if we volume down (with key combination: Fn+F6, you can also emulate the keys with "xdotool key XF86AudioLowerVolume") to zero then logout and back in. But if we just zero down volume(with the single volume on/off button), then logout and back in, the volume icon is still there. This issue is fixed with installing indicator- sound_12.10.2+14.10.20141010-0ubuntu1(Utopic) Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Feb 11 14:18:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-datong140729-trusty-amd64-20150114-3 InstallationDate: Installed on 2015-01-29 (13 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150114-08:50 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1420630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: New Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 "sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove "compiz" from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after "export COMPIZ_CONFIG_PROFILE": env UNITY_LOW_GFX_MODE="1" export UNITY_LOW_GFX_MODE" We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
Tammy, Can you check if you can only reproduce it when you reveal the launcher with alt-f1? Thanks, Ara. ** Changed in: oem-priority Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Incomplete Status in “unity” package in Ubuntu: Invalid Bug description: To Reproduce: 1. Set the Launcher to autohide 2. On any system (have tried on some Dell systems and some HP systems) which supports single touch 3. Touch the screen and try to move cursor to show launcher Expected result: Launcher can reveal Actual result: Launcher "cannot" reveal Additional information: 1. When the issue happens, can press window key to show dash and launcher, but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
** Changed in: oem-priority Status: Incomplete => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: To Reproduce: 1. Set the Launcher to autohide 2. On any system (have tried on some Dell systems and some HP systems) which supports single touch 3. Touch the screen and try to move cursor to show launcher Expected result: Launcher can reveal Actual result: Launcher "cannot" reveal Additional information: 1. When the issue happens, can press window key to show dash and launcher, but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
** Description changed: - To Reproduce: + To Reproduce (in a system with a touch screen) - 1. Set the Launcher to autohide + 1. Boot the system and don't touch the screen + 2. Set the Launcher to autohide + 3. Move the cursor to the left (using the touchpad or an external mouse) + 4. The Launcher is revealed successfully + 5. Wait until the launcher hides again + 6. Now, touch the screen for the first time (no matter where you touch the screen) + 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher - 2. On any system (have tried on some Dell systems and some HP systems) - which supports single touch - - 3. Touch the screen and try to move cursor to show launcher - - Expected result: Launcher can reveal - Actual result: Launcher "cannot" reveal + Expected result: Launcher is revealed + Actual result: Launcher cannot be revealed. Additional information: - 1. When the issue happens, can press window key to show dash and launcher, but moving cursor to the left side still can't show launcher - + 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz - 3. Switch to ttyl1 and restart lightdm can recover -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: To Reproduce (in a system with a touch screen) 1. Boot the system and don't touch the screen 2. Set the Launcher to autohide 3. Move the cursor to the left (using the touchpad or an external mouse) 4. The Launcher is revealed successfully 5. Wait until the launcher hides again 6. Now, touch the screen for the first time (no matter where you touch the screen) 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher Expected result: Launcher is revealed Actual result: Launcher cannot be revealed. Additional information: 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
** Also affects: unity (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Confirmed Status in Unity 5.0 series: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Precise: New Bug description: To Reproduce (in a system with a touch screen) 1. Boot the system and don't touch the screen 2. Set the Launcher to autohide 3. Move the cursor to the left (using the touchpad or an external mouse) 4. The Launcher is revealed successfully 5. Wait until the launcher hides again 6. Now, touch the screen for the first time (no matter where you touch the screen) 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher Expected result: Launcher is revealed Actual result: Launcher cannot be revealed. Additional information: 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen
** Changed in: oem-priority Importance: Undecided => High ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Stephen M. Webb (bregma) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223739 Title: Launcher - unable to reveal Launcher under autohide after using the touch screen Status in OEM Priority Project: Confirmed Status in Unity 5.0 series: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Precise: New Bug description: To Reproduce (in a system with a touch screen) 1. Boot the system and don't touch the screen 2. Set the Launcher to autohide 3. Move the cursor to the left (using the touchpad or an external mouse) 4. The Launcher is revealed successfully 5. Wait until the launcher hides again 6. Now, touch the screen for the first time (no matter where you touch the screen) 7. Now, use again the touchpad or external mouse to move the cursor to the left to reveal the Launcher Expected result: Launcher is revealed Actual result: Launcher cannot be revealed. Additional information: 1. When the issue happens, can press window key to show dash and launcher (or alt-f1 to reveal the launcher), but moving cursor to the left side still can't show launcher 2. There is no crash is observed so far on X or Compiz 3. Switch to ttyl1 and restart lightdm can recover To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1223739/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
