[Desktop-packages] [Bug 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin
> I can confirm that toggling repeat keys off and on again fixes the issue temporarily for the current session. Also changing the repeat speed. It would be nice if this toggling would be possible from CLI. This way I wouldn't have to go in the settings every time my computer woke up from sleep. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/427168 Title: usb keyboard settings (repeat rate and delay) reset on plugin Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: I like a fairly fast repeat rate and low delay when typing. In the course of using my laptop (Dell Vostro 1500), I sometimes plug in a USB keyboard. Every time I do this, I notice that the repeat rate and delay on the USB keyboard are way slow and high, while the built-in keyboard repeat rate and delay are as I like them (fast and low). To fix this, every time I plug in the USB keyboard, I have to go to System→Preferences→Keyboard, slightly move the Speed slider, then Close the dialog. (Note that the sliders haven't changed from the last invocation of this application, just that the settings apparently need to be reapplied internally.) I believe that at least these keyboard settings (repeat rate and delay) should be universal for all keyboards. Repeatable: always. How to reproduce: 1. plug in a USB keyboard 2. Note current repeat-rate and delay. 3. Change repeat-rate and delay via System->Preferences->Keyboard 4. Unplug and re-plugin the USB keyboard. 5. Return to step 2. Possibly related bugs: Bug #295990 Bug #426176 $ uname -a Linux hani 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/427168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin
Bug is still happening on Ubuntu 20.04.1 LTS. I'm using an external Apple Alu Keyboard. The interesting thing is, that repeat rate and delay are correct for the internal keyboard of the notebook but they are wrong for the plugged in keyboard. If I go into settings and set it again it is correct for this session. But it will be reset on the next time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/427168 Title: usb keyboard settings (repeat rate and delay) reset on plugin Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: I like a fairly fast repeat rate and low delay when typing. In the course of using my laptop (Dell Vostro 1500), I sometimes plug in a USB keyboard. Every time I do this, I notice that the repeat rate and delay on the USB keyboard are way slow and high, while the built-in keyboard repeat rate and delay are as I like them (fast and low). To fix this, every time I plug in the USB keyboard, I have to go to System→Preferences→Keyboard, slightly move the Speed slider, then Close the dialog. (Note that the sliders haven't changed from the last invocation of this application, just that the settings apparently need to be reapplied internally.) I believe that at least these keyboard settings (repeat rate and delay) should be universal for all keyboards. Repeatable: always. How to reproduce: 1. plug in a USB keyboard 2. Note current repeat-rate and delay. 3. Change repeat-rate and delay via System->Preferences->Keyboard 4. Unplug and re-plugin the USB keyboard. 5. Return to step 2. Possibly related bugs: Bug #295990 Bug #426176 $ uname -a Linux hani 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/427168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880961] Re: Deja dup allow multiple backup locations, destination and schedules.
Sounds like a duplicate of https://bugs.launchpad.net/deja- dup/+bug/324631 for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1880961 Title: Deja dup allow multiple backup locations, destination and schedules. Status in deja-dup package in Ubuntu: New Bug description: If someone wants to save their external hard drive to AWS and their main SSD to google drive, currently (to my knowlage) this is impossible. With the ability to choose multiple Backups a lot of extra utility would be possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1880961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype
This bug is still present on Ubuntu 20.04. Also you can find it on other places like https://ubuntuforums.org/showthread.php?t=2398097 https://discourse.ubuntubudgie.org/t/online-accounts-cant-copy-and-paste-email-password/3212/3 or https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1510011 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867982] Re: unable to copy and paste login and password
*** This bug is a duplicate of bug 1703377 *** https://bugs.launchpad.net/bugs/1703377 ** This bug has been marked a duplicate of bug 1703377 Gnome online account login prevents paste or autotype -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1867982 Title: unable to copy and paste login and password Status in gnome-online-accounts package in Ubuntu: New Bug description: Select eg Google account when you have your user and password in clipboard. In the new account interface, cant paste into fields. Expected is paste. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu Mar 19 08:37:01 2020 InstallationDate: Installed on 2020-03-15 (2 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1867982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750087] Re: [libreoffice-kde4] LO crashes when trying to save
I can confirm that this issue is still present in 1:6.0.7-0ubuntu0.18.04.10. the command $ sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.* still works though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1750087 Title: [libreoffice-kde4] LO crashes when trying to save Status in libreoffice package in Ubuntu: Fix Released Bug description: To reproduce type hello world into a libreoffice document. Then press the save icon. libreoffice crashes. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 to try to save and then try it crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Feb 16 16:19:38 2018 InstallationDate: Installed on 2017-06-20 (241 days ago) InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170619) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-02-02 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
The bug is still present for me and I have the feeling that this bug somehow also might be related to the issues https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845810 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage
…and could this issue be related to this one? https://bugzilla.redhat.com/show_bug.cgi?id=1668808 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage
I'm having the same problem on Ubuntu 18.04.3 LTS. gsd-xsettings is the reason my system is even fully filling the SWAP. Is there any possibility to debug this? ** Bug watch added: Red Hat Bugzilla #1668808 https://bugzilla.redhat.com/show_bug.cgi?id=1668808 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError
Okay so this explains everything: in my case the fault was not about special characters in files or filenames but of error messages. I executed Deja Dup / Duplicity in a localized environment and got an error. If the *error message* contains special characters the response in the view won't show the real message at all. Instead the error message will cause the encoding exception. In my case it was: […] DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 124, in __copy_file DUPLICITY: . None, self.__copy_progress, None) DUPLICITY: . Error: g-io-error-quark: Fehler beim Senden von Daten: Datenübergabe unterbrochen (broken pipe) (44) DUPLICITY: . […] So it seems that the error could be everything. As long as it contains special characters it will lead to the encoding issue. In my case switching the locale showed the real cause in the GUI. I hope this information helps someone else too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1736164 Title: deja-dup/duplicity backup fails with UnicodeDecodeError Status in Déjà Dup: Triaged Status in Duplicity: New Status in deja-dup package in Ubuntu: Triaged Status in deja-dup package in Fedora: Fix Released Bug description: See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873 Description of problem: With the update from Fedora 25 to Fedora 26 Workstation, backups with deja-dup/duplicity are failing Version-Release number of selected component (if applicable): duplicity 0.7.13.1 deja-dup 34.3 How reproducible: Always (scheduled and manually started backup) Steps to Reproduce: 1. Wait for the scheduled backup to start or start it via the "Backup now" button 2. Some or a large number of files might get backed up, then the backup stops with "Failed with an unknown error" 3. Actual results: Backup fails Expected results: Backup completes as it always did Additional info: Traceback (most recent call last): File "/usr/bin/duplicity", line 1540, in with_tempdir(main) File "/usr/bin/duplicity", line 1534, in with_tempdir fn() File "/usr/bin/duplicity", line 1385, in main do_backup(action) File "/usr/bin/duplicity", line 1516, in do_backup incremental_backup(sig_chain) File "/usr/bin/duplicity", line 668, in incremental_backup globals.backend) File "/usr/bin/duplicity", line 453, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 146, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 452, in vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 341, in put backend.put(tdp, dest_filename) File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, in inner_retry % exception_traceback()) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in exception_traceback return uexc(msg) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in uexc e = unicode(e).encode('utf-8') UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1736164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError
This bug is rather https://bugs.launchpad.net/duplicity/+bug/1386373 — right? As it seems that there's a fix in Fedora somewhere[1]: is there any chance to get this upstream fix on Ubuntu 18.04 LTS as well? I mean, I would love to have a working backup solution again. ;) Also the error message seems to be caused by totally different problems!? 1. a read encoding issue: https://bugs.launchpad.net/duplicity/+bug/1386373 (because the suggested fix seem to work for Eugene) 2. readonly mount https://bugs.launchpad.net/deja-dup/+bug/1769891#yui_3_10_3_1_1545160806792_1239 and https://bugs.launchpad.net/deja-dup/+bug/1741769 So I guess the error message in general is or was very misleading!? [1] Should the patch be visible on https://bugzilla.redhat.com/show_bug.cgi?id=1470873 ? I can't see it!? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1736164 Title: deja-dup/duplicity backup fails with UnicodeDecodeError Status in Déjà Dup: Triaged Status in Duplicity: New Status in deja-dup package in Ubuntu: Triaged Status in deja-dup package in Fedora: Fix Released Bug description: See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873 Description of problem: With the update from Fedora 25 to Fedora 26 Workstation, backups with deja-dup/duplicity are failing Version-Release number of selected component (if applicable): duplicity 0.7.13.1 deja-dup 34.3 How reproducible: Always (scheduled and manually started backup) Steps to Reproduce: 1. Wait for the scheduled backup to start or start it via the "Backup now" button 2. Some or a large number of files might get backed up, then the backup stops with "Failed with an unknown error" 3. Actual results: Backup fails Expected results: Backup completes as it always did Additional info: Traceback (most recent call last): File "/usr/bin/duplicity", line 1540, in with_tempdir(main) File "/usr/bin/duplicity", line 1534, in with_tempdir fn() File "/usr/bin/duplicity", line 1385, in main do_backup(action) File "/usr/bin/duplicity", line 1516, in do_backup incremental_backup(sig_chain) File "/usr/bin/duplicity", line 668, in incremental_backup globals.backend) File "/usr/bin/duplicity", line 453, in write_multivol (tdp, dest_filename, vol_num))) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 146, in schedule_task return self.__run_synchronously(fn, params) File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line 172, in __run_synchronously ret = fn(*params) File "/usr/bin/duplicity", line 452, in vol_num: put(tdp, dest_filename, vol_num), File "/usr/bin/duplicity", line 341, in put backend.put(tdp, dest_filename) File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376, in inner_retry % exception_traceback()) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in exception_traceback return uexc(msg) File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in uexc e = unicode(e).encode('utf-8') UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1736164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
This issue still appears on Ubuntu 18.04. The variant "options snd-hda-intel single_cmd=1 probe_mask=1 model=dell- headset-multi" doesn't work and the Pin override with hdajackretask doesn't work neither. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
I can't confirm what Kasey (kasey-erickson) wrote: issue still appears in Ubuntu 17.10. I upgraded from 17.04. So if it really should be fixed in 17.10 I'm very open to hints for particular config purges/reinstallations or actually anything that could help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
I can confirm what Jess (jbermudes) wrote: issue can't be solved in 17.04 with the proposal so I hope for the best in 17.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?
It looks like I just ran into this issue with Ubuntu 16.10 so the upstart reference may be wrong here. Is any more data needed or would it be useless anyway? PS: It seems that some of the "fixes" made it to /etc/init/lightdm.conf already but nothing helps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in upstart : Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017
Having the same issue on Dell XPS 9550 with GM107M [GeForce GTX 960M] on Ubuntu 16.10. On the other hand: if you google this people are having these issues for years with nvidia drivers. I would love how to debug this at least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1663926 Title: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017 Status in Nvidia: New Status in nvidia-prime package in Ubuntu: Confirmed Bug description: There have been multiple reports that "nvidia-prime select intel" results in a black screen on the new Dell XPS 15 (9560, with Nvidia 1050) See the following threads: 1. (initial report). https://www.reddit.com/r/Ubuntu/comments/5qjq4v/dell_xps_15_kaby_lake_w_nvidia_1050_review_2017/ 2. (lots of confirmations of the same thing) https://www.reddit.com/r/Dell/comments/5rxb5x/any_dell_xps_15_9560_linux_users/ 3. (additional confirmation) https://www.reddit.com/r/Dell/comments/5t2b5d/high_cpu_temp_and_fan_usage_for_ubuntu_on_9560/ 4. (reported on Nvidia forums) https://devtalk.nvidia.com/default/topic/991853/complete-freeze-with-nvidia-prime/ To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1663926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310745] Re: keep custom resolutions
I have to correct myself. I have to launch an application first otherwise the resolution falls back down to 1920. that is not correct: the issue seems also to be time related. If I wait after logging in the resolution will be more probable accepted. Additionally some applications seem to make it impossible to get the higher resolution (for example HipChat). On the start the resolution will fall back immediately and it is impossible to increase it as long as the application is open. On applications like eog or the ubuntu system settings, the resolution will also fallback to the lower, but after execution the xrandr-commands again, the resolution will be accepted by the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1310745 Title: keep custom resolutions Status in “unity-settings-daemon” package in Ubuntu: New Bug description: I work with an ASUS Zenbook UX31A and put it on the Dell monitor U2711. The Zenbook has HDMI output. While the monitor supports 2560x1600 there is always just max 1920x1080 selectable due to wrong EDID-informations (I am not entirely sure about the cause anymore). That wasn't a (big) problem for me, until now, while the ubuntu wiki describes how to add undetected resolutions ( https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions ). When I attached the Dell monitor I just executed a shell script which adds the modes as described in the wiki. Now I updated to Ubuntu 14.04 LTS which changed the game: When I start Unity, I have to launch an application first otherwise the resolution falls back down to 1920. When I have the 2560-resolution and I open the ubuntu settings, the resolution falls back again. When I start the image viewer (eog), the resolution falls back again. This is really annoying and it would be great if there would be a solution. PS: this where the lines I used (I got them from a forum) xrandr --newmode 2560x1440_35.00 173.58 2560 2696 2968 3376 1440 1441 1444 1469 -HSync +Vsync xrandr --addmode HDMI1 2560x1440_35.00 xrandr --output HDMI1 --mode 2560x1440_35 --output eDP1 --off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1310745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357665] [NEW] UI is useless if having two monitors and using just the external one
Public bug reported: When I am home, I put my notebook on an external monitor and just use this one. While this causes already pain since 14.04 [1], I noticed that the UI for the login is absolutely useless for someone who doesn't how the multi-monitor-functionality on lightdm works. If the integrated monitor is off and I am just using the external one, lightdm shows the login screen on the integrated monitor anyway (the login screen is therefore invisible). What I can see in this moment is just a screen with the Ubuntu logo. No cursor, no message and nothing else that could tell the user that he can login now. So even if the behaviour, that the login screen would be shown on the correct monitor, it would be useful to give the user a hint how he could login (while it could be that he is looking on the wrong monitor). For example an arrow on the edge which indicates where the cursor is. So if someone moves the mouse he will see, that the mouse still works (which isn't the case now). And somehow it should be communicated, that the login screen is on another monitor (something which says hey, the login screen you are looking for is on the left side, so you have to move the mouse cursor on the right side if you want to see it.). [1] https://bugs.launchpad.net/ubuntu/+source/unity-settings- daemon/+bug/1310745 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1357665 Title: UI is useless if having two monitors and using just the external one Status in “lightdm” package in Ubuntu: New Bug description: When I am home, I put my notebook on an external monitor and just use this one. While this causes already pain since 14.04 [1], I noticed that the UI for the login is absolutely useless for someone who doesn't how the multi-monitor-functionality on lightdm works. If the integrated monitor is off and I am just using the external one, lightdm shows the login screen on the integrated monitor anyway (the login screen is therefore invisible). What I can see in this moment is just a screen with the Ubuntu logo. No cursor, no message and nothing else that could tell the user that he can login now. So even if the behaviour, that the login screen would be shown on the correct monitor, it would be useful to give the user a hint how he could login (while it could be that he is looking on the wrong monitor). For example an arrow on the edge which indicates where the cursor is. So if someone moves the mouse he will see, that the mouse still works (which isn't the case now). And somehow it should be communicated, that the login screen is on another monitor (something which says hey, the login screen you are looking for is on the left side, so you have to move the mouse cursor on the right side if you want to see it.). [1] https://bugs.launchpad.net/ubuntu/+source/unity-settings- daemon/+bug/1310745 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1357665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1318334] [NEW] Most of the launcher and top bar freeze occasionally
Public bug reported: I think this happens mostly after locking and unlocking again. Clicking on the trash bin works as well as the tray icons. I switch the focussed application the title bar also changes but I am unable to reach the application menu. Launching applications by clicking on the launcher icons doesn't work but the icons refresh themselves on state differences. So I am able to see wether an application is started and the workspace indicator also refreshes. I am running Ubuntu 14.04 with Unity 7.2.0+14.04.20140423-0ubuntu1.2 and this problem is available since I upgraded to 14.04. This bugs me a lot (happens on a daily basis). PS: it is currently frozen if that helps in the combination with the data from apport ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CurrentDesktop: Unity Date: Sun May 11 14:41:59 2014 InstallationDate: Installed on 2012-09-29 (588 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (21 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 Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1318334 Title: Most of the launcher and top bar freeze occasionally Status in “unity” package in Ubuntu: New Bug description: I think this happens mostly after locking and unlocking again. Clicking on the trash bin works as well as the tray icons. I switch the focussed application the title bar also changes but I am unable to reach the application menu. Launching applications by clicking on the launcher icons doesn't work but the icons refresh themselves on state differences. So I am able to see wether an application is started and the workspace indicator also refreshes. I am running Ubuntu 14.04 with Unity 7.2.0+14.04.20140423-0ubuntu1.2 and this problem is available since I upgraded to 14.04. This bugs me a lot (happens on a daily basis). PS: it is currently frozen if that helps in the combination with the data from apport ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CurrentDesktop: Unity Date: Sun May 11 14:41:59 2014 InstallationDate: Installed on 2012-09-29 (588 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1318334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310745] Re: keep custom resolutions
I have to add that the whole resolution setting process I described above became so complicated with ubuntu 14.04 that I have to execute these commands a few times until this works. Sometimes it seem to setup an even smaller resolution while the mouse cursor is setup for another resolution. So you can't use the mouse while the rendering of the mouse cursor doesn't match to the real position of the cursor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1310745 Title: keep custom resolutions Status in “unity-settings-daemon” package in Ubuntu: New Bug description: I work with an ASUS Zenbook UX31A and put it on the Dell monitor U2711. The Zenbook has HDMI output. While the monitor supports 2560x1600 there is always just max 1920x1080 selectable due to wrong EDID-informations (I am not entirely sure about the cause anymore). That wasn't a (big) problem for me, until now, while the ubuntu wiki describes how to add undetected resolutions ( https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions ). When I attached the Dell monitor I just executed a shell script which adds the modes as described in the wiki. Now I updated to Ubuntu 14.04 LTS which changed the game: When I start Unity, I have to launch an application first otherwise the resolution falls back down to 1920. When I have the 2560-resolution and I open the ubuntu settings, the resolution falls back again. When I start the image viewer (eog), the resolution falls back again. This is really annoying and it would be great if there would be a solution. PS: this where the lines I used (I got them from a forum) xrandr --newmode 2560x1440_35.00 173.58 2560 2696 2968 3376 1440 1441 1444 1469 -HSync +Vsync xrandr --addmode HDMI1 2560x1440_35.00 xrandr --output HDMI1 --mode 2560x1440_35 --output eDP1 --off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1310745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns
This is especially nasty while nautilus doesn't really distinguish between the filetypes anymore. So an .epub, .doc, .mobi, .odt and a .pdf will always show as 'Document' in the type column. While I am interested in the in the real filetype, I had to remove the type column and add the mime-type column which made the 'too small name column' just worse while mime types are very big. You can't even make the mime-type column smaller, so that bug here just made nautilus unusable for me. If even would switch to nautilus again if this mega-package of bugs would be fixed. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1243806 Title: The names column has its width dictated by other columns Status in Nautilus: Confirmed Status in “nautilus” package in Ubuntu: Triaged Status in “nautilus” source package in Trusty: Triaged Bug description: Folder names in Location area keeps the width even though when I go back to upper folder. First of all this new downgraded nautilus folder section holds its width and I cannot even change the width at all. Then when I go deep down lower folders or open folder with long name, it would squeeze down the Name part and I cannot even see names anymore. Then when I go up to upper folder or root, I cannot see the names anymore becaue location column takes up all the space. Once I click one of the unseen folder, I may see the names again. This is one of too many problems of 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1243806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310745] [NEW] keep custom resolutions
Public bug reported: I work with an ASUS Zenbook UX31A and put it on the Dell monitor U2711. The Zenbook has HDMI output. While the monitor supports 2560x1600 there is always just max 1920x1080 selectable due to wrong EDID-informations (I am not entirely sure about the cause anymore). That wasn't a (big) problem for me, until now, while the ubuntu wiki describes how to add undetected resolutions ( https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions ). When I attached the Dell monitor I just executed a shell script which adds the modes as described in the wiki. Now I updated to Ubuntu 14.04 LTS which changed the game: When I start Unity, I have to launch an application first otherwise the resolution falls back down to 1920. When I have the 2560-resolution and I open the ubuntu settings, the resolution falls back again. When I start the image viewer (eog), the resolution falls back again. This is really annoying and it would be great if there would be a solution. PS: this where the lines I used (I got them from a forum) xrandr --newmode 2560x1440_35.00 173.58 2560 2696 2968 3376 1440 1441 1444 1469 -HSync +Vsync xrandr --addmode HDMI1 2560x1440_35.00 xrandr --output HDMI1 --mode 2560x1440_35 --output eDP1 --off ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1310745 Title: keep custom resolutions Status in “unity-control-center” package in Ubuntu: New Bug description: I work with an ASUS Zenbook UX31A and put it on the Dell monitor U2711. The Zenbook has HDMI output. While the monitor supports 2560x1600 there is always just max 1920x1080 selectable due to wrong EDID-informations (I am not entirely sure about the cause anymore). That wasn't a (big) problem for me, until now, while the ubuntu wiki describes how to add undetected resolutions ( https://wiki.ubuntu.com/X/Config/Resolution#Adding_undetected_resolutions ). When I attached the Dell monitor I just executed a shell script which adds the modes as described in the wiki. Now I updated to Ubuntu 14.04 LTS which changed the game: When I start Unity, I have to launch an application first otherwise the resolution falls back down to 1920. When I have the 2560-resolution and I open the ubuntu settings, the resolution falls back again. When I start the image viewer (eog), the resolution falls back again. This is really annoying and it would be great if there would be a solution. PS: this where the lines I used (I got them from a forum) xrandr --newmode 2560x1440_35.00 173.58 2560 2696 2968 3376 1440 1441 1444 1469 -HSync +Vsync xrandr --addmode HDMI1 2560x1440_35.00 xrandr --output HDMI1 --mode 2560x1440_35 --output eDP1 --off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1310745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
Yes, obviously this seems to be anyhow tricky. Some people say that A2DP doesn't support unidirectionaly streams (ie D. Brodzik and SpudULike here in this thread or like nick parlante found out by googling). Some people say that it is possible but there are no headsets supporting it ( http://osdir.com/ml/linux.bluez.devel/2005-01/msg00187.html ) [1]. Otherwise it is working in other operating systems and also wikipedia says that is designed to transfer a *uni-directional* 2-channel stereo audio stream ( http://en.wikipedia.org/wiki/A2DP#Advanced_Audio_Distribution_Profile_.28A2DP.29 ). I don't have any clue about, what things are working and what aren't. I just see the problem. What would help: 2011 Alexander Skwar asked wether it is possible at least to switch the profiles automatically, depending on what are you doing (A2DP everytime you are just listening and HSP when starting a call with ekiga/skype). Colin Guthrie responded that they are working on it ( http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-September/011296.html / http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-September/011300.html ). But at least on my computer now with Ubuntu 13.04 and ASUS Zenbook UX31A, the standard choosen profile is HSP and therefore terrible sounding. Anyhow, I also doesn't have the impression that we are making any progress here. :-) [1] I have to admit that this message is from 2005 and not up-to-date for sure . I just wanted to show that you will find many facts and opinions in the web. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/508522 Title: Mic is not available with A2DP Bluetooth profile Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles HSP/ HFP Telephony duplex and A2DP High Fidelity Playback. For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or telephone quality with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 449208] Re: touchpad tap-to-click response delayed .5 seconds
Actually I also had the impression that the touchpad responds somehow slow. I use a ASUS Zenbook UX31A and found this bug report by accident. While everything else is configurable via gui settings the tap to click response is just slow. For me synclient FastTaps=1 MaxDoubleTapTime=100 fixed the problem but I don't understand why it isn't the default. I know other people which use Ubuntu and sometimes tap a few times because the default settings just feel unresponsive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/449208 Title: touchpad tap-to-click response delayed .5 seconds Status in “xserver-xorg-input-synaptics” package in Ubuntu: Expired Bug description: Binary package hint: xserver-xorg-input-mouse This almost seems related to bug # 54191, but I can't reproduce it the way that bug states. I'm running Karmic Koala fully updated and just enabled Enable mouse clicks with touchpad using the gnome-mouse- properties GUI. While it now accepts left-clicks by tapping the touchpad, it seems to take about 1/2 seconds for it to respond. The left mouse hard-buttons (above and below the touchpad) still respond immediately. hardware is Latitude D630 Synaptics Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/449208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 667662] Re: User unable to save attached/embedded images
I am using Evolution 3.8.2 and there is no possibility anymore (again) to save an image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/667662 Title: User unable to save attached/embedded images Status in The Evolution Mail Calendaring Tool: New Status in “evolution” package in Ubuntu: Incomplete Bug description: Binary package hint: evolution User received email with embedded images as forwarded message, evolution 2.30.3 rendered images correctly but didn't allow user to save images. When selecting image, user were only prompted with context menu option of coping image or saving whole email but not the image alone. Coping option didn't allow user to paste image in to Desktop folder. Expected results: When same email was forwarded to Mac OSX Mail client, an attachments were detected correctly and allowed user to easily extract images in form of attachment. Same process should be applied to Evolution mail client. Ubuntu 10.10 Amd64 Evolution 2.30.3 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Oct 28 10:14:19 2010 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_GB.utf8 SourcePackage: evolution To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/667662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082972] Re: Launching apps with pkexec exits before I am able to type the password
*** This bug is a duplicate of bug 1077546 *** https://bugs.launchpad.net/bugs/1077546 ** This bug has been marked a duplicate of bug 1077546 Gnome Shell sudo dialog said Sorry, that didn't work. Please try again when opening Synaptic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1082972 Title: Launching apps with pkexec exits before I am able to type the password Status in “policykit-1” package in Ubuntu: Confirmed Bug description: If I want to open an application which needs su rights via pkexec I am able to type some characters until the message follows Entschuldigung, das hat nicht geklappt. Bitte versuchen Sie es erneut. (it is german but I don't know the exact original string or find the original string out in an easy way. It says something like Sorry but that did not work. Please try again) and the dialogue disappears before I am able to complete my passphrase or press return key. Initially I found the bug by trying to start applications (ie gparted) via gnome shell. I am using x64 Ubuntu 12.10 with gnome 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1082972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
I have the same problem in x64 Ubuntu and Gnome. Since 12.10 display management absolutely doesn't work for me on new user accounts. Displays are rarely selectable and switching to some unspectacular configurations lead to graphical errors, black screen or logouts. I use an ASUS Zenbook UX31A with DELL U2711 via HDMI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1079538] Re: Displays Console - Can't Choose Other Monitor Until After Apply
*** This bug is a duplicate of bug 1043769 *** https://bugs.launchpad.net/bugs/1043769 ** This bug has been marked a duplicate of bug 1043769 Monitor image not clickable in display settings after the first time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1079538 Title: Displays Console - Can't Choose Other Monitor Until After Apply Status in “gnome-control-center” package in Ubuntu: New Bug description: Under All Settings Displays, if I choose a particular monitor to configure, clicking on another monitor won't select that monitor until after I've hit the apply button. Therefore, this prevents me from configuring both of my monitors before I hit the apply button. You can no longer click-toggle between monitors; you must apply the settings of the first monitor you selected before viewing the settings of a second monitor. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 15 23:29:08 2012 InstallationDate: Installed on 2012-10-19 (28 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1079538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082972] [NEW] Launching apps with pkexec exits before I am able to type the password
Public bug reported: If I want to open an application which needs su rights via pkexec I am able to type some characters until the message follows Entschuldigung, das hat nicht geklappt. Bitte versuchen Sie es erneut. (it is german but I don't know the exact original string or find the original string out in an easy way. It says something like Sorry but that did not work. Please try again) and the dialogue disappears before I am able to complete my passphrase or press return key. Initially I found the bug by trying to start applications (ie gparted) via gnome shell. I am using x64 Ubuntu 12.10 with gnome 3. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1082972 Title: Launching apps with pkexec exits before I am able to type the password Status in “policykit-1” package in Ubuntu: New Bug description: If I want to open an application which needs su rights via pkexec I am able to type some characters until the message follows Entschuldigung, das hat nicht geklappt. Bitte versuchen Sie es erneut. (it is german but I don't know the exact original string or find the original string out in an easy way. It says something like Sorry but that did not work. Please try again) and the dialogue disappears before I am able to complete my passphrase or press return key. Initially I found the bug by trying to start applications (ie gparted) via gnome shell. I am using x64 Ubuntu 12.10 with gnome 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1082972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082972] Re: Launching apps with pkexec exits before I am able to type the password
The installed version of policykit-1 is 0.104-2ubuntu1. ** Package changed: alsa-driver (Ubuntu) = policykit-1 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1082972 Title: Launching apps with pkexec exits before I am able to type the password Status in “policykit-1” package in Ubuntu: New Bug description: If I want to open an application which needs su rights via pkexec I am able to type some characters until the message follows Entschuldigung, das hat nicht geklappt. Bitte versuchen Sie es erneut. (it is german but I don't know the exact original string or find the original string out in an easy way. It says something like Sorry but that did not work. Please try again) and the dialogue disappears before I am able to complete my passphrase or press return key. Initially I found the bug by trying to start applications (ie gparted) via gnome shell. I am using x64 Ubuntu 12.10 with gnome 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1082972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082972] Re: Launching apps with pkexec exits before I am able to type the password
In the console appears: Error executing command as another user: Not authorized This incident has been reported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1082972 Title: Launching apps with pkexec exits before I am able to type the password Status in “policykit-1” package in Ubuntu: New Bug description: If I want to open an application which needs su rights via pkexec I am able to type some characters until the message follows Entschuldigung, das hat nicht geklappt. Bitte versuchen Sie es erneut. (it is german but I don't know the exact original string or find the original string out in an easy way. It says something like Sorry but that did not work. Please try again) and the dialogue disappears before I am able to complete my passphrase or press return key. Initially I found the bug by trying to start applications (ie gparted) via gnome shell. I am using x64 Ubuntu 12.10 with gnome 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1082972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970608] Re: Multi-touch touchpad not working (Asus UX31)
Works for me since 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/970608 Title: Multi-touch touchpad not working (Asus UX31) Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: The multi-touch touchnad does not work on an Asus UX31. This means, for example, that you can't click on a window with the click button and move it with the sensitive area of the touchpad. (This particular touchpad's sensitive area extends onto the buttons. The touchpad works fine with Windows, so it's very likely a driver issue.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.5.99.902-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Sun Apr 1 08:17:47 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MachineType: ASUSTeK Computer Inc. UX31E ProcEnviron: TERM=xterm LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic root=UUID=3698f1d7-5c60-473c-b752-c98e427883f7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/970608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051920] Re: compress file dialog does not compress file with password
I works now on my system. Obviously this bug got fixed!? ** Changed in: nautilus (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1051920 Title: compress file dialog does not compress file with password Status in “nautilus” package in Ubuntu: Fix Released Bug description: compress file dialog does not compress file with password even I enter the password in related field. the compressed file is generated, but, no password is asked while opening that file. rar, zip both does not compress files with password enabled in compression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Mon Sep 17 15:00:38 2012 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+65+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'318' InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1051920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051920] Re: compress file dialog does not compress file with password
I am pretty sure that this bug affects much more users but most people doesn't check their archives again. So in my opinion, people thinking that their archives are secure but in reality they are absolutely unencrypted, could be really critical in some cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1051920 Title: compress file dialog does not compress file with password Status in “nautilus” package in Ubuntu: Confirmed Bug description: compress file dialog does not compress file with password even I enter the password in related field. the compressed file is generated, but, no password is asked while opening that file. rar, zip both does not compress files with password enabled in compression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Mon Sep 17 15:00:38 2012 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+65+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'318' InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=tr_TR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1051920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902792] Re: Creating metacontacts does not work
*** This bug is a duplicate of bug 847078 *** https://bugs.launchpad.net/bugs/847078 Thank you very much for marking this bug as a duplicate. It was really the absence of the package libfolks-eds25 as mentioned in #847078. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/902792 Title: Creating metacontacts does not work Status in “empathy” package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) NonfreeKernelModules: wl fglrx Package: empathy 3.2.0.1-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/902792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902792] Re: Creating metacontacts does not work
No, I am just using a single XMPP-account. So this would be the log gabble (jabber)? Or do you mean a different log (mission-control, Logger or Empathy.Chat)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/902792 Title: Creating metacontacts does not work Status in “empathy” package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) NonfreeKernelModules: wl fglrx Package: empathy 3.2.0.1-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/902792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902792] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/902792/+attachment/2627986/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/902792 Title: Creating metacontacts does not work Status in “empathy” package in Ubuntu: New Bug description: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) NonfreeKernelModules: wl fglrx Package: empathy 3.2.0.1-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/902792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902792] [NEW] Creating metacontacts does not work
Public bug reported: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) NonfreeKernelModules: wl fglrx Package: empathy 3.2.0.1-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected oneiric ** Tags added: apport-collected oneiric ** Description changed: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. - Obviously I'm not the only one who is affected by this bug: - http://ubuntuforums.org/showthread.php?p=11498961 + Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 + --- + ApportVersion: 1.23-0ubuntu4 + Architecture: amd64 + DistroRelease: Ubuntu 11.10 + EcryptfsInUse: Yes + InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) + NonfreeKernelModules: wl fglrx + Package: empathy 3.2.0.1-0ubuntu1.1 + PackageArchitecture: amd64 + ProcEnviron: + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 + Tags: oneiric + Uname: Linux 3.0.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/902792 Title: Creating metacontacts does not work Status in “empathy” package in Ubuntu: New Bug description: I have a fresh Ubuntu 11.10 installation. If I try to create a metacontact nothing happens (besides the metacontact creation window closes).e The contacts are still separate. Of course I would expect, that a new metacontact was created. I' pretty sure that this worked on my old computer where I updated to Ubuntu 11.10. Obviously I'm not the only one who is affected by this bug: http://ubuntuforums.org/showthread.php?p=11498961 --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) NonfreeKernelModules: wl fglrx Package: empathy 3.2.0.1-0ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/902792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp