[Desktop-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
Hm... i didn't check quickly enough, but according to the timestamp on the below `dmesg --kernel --human` output (about the time I first experienced this bug), this bug *might* be related to this keycodes error...: [Jul22 17:45] atkbd serio0: Unknown key pressed (translated set 2, code 0xa8 on isa0060/serio0). [ +0.04] atkbd serio0: Use 'setkeycodes e028 ' to make it known. [ +15.411721] atkbd serio0: Unknown key pressed (translated set 2, code 0xa9 on isa0060/serio0). [ +0.07] atkbd serio0: Use 'setkeycodes e029 ' to make it known. But I don't know enough about that log message to decide either way. -- 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/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
Adrian: no, not lightdm-specific. This just happened to me for the first
time today and I'm using gdm3 and gnome3.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
If anyone could shed light on what logs might be checked, to debug *how*
this change magically comes about, that would be helpful[1] to finding a
solution. (where "solution" is: this behavior shouldn't get enabled
unexpectedly).
[1]: I personally haven't a clue how this happened. I just installed a
`snap` package ("shotcut") for the first time ever, and "openshot" via
`apt`, then a few minutes later found this was happening.
--
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/1508146
Title:
alt + left/right arrows switch between tty consoles, cannot disable
Status in gnome-shell package in Ubuntu:
Confirmed
Status in lightdm package in Ubuntu:
Confirmed
Bug description:
I'm used to using alt+left/right arrow to navigate back and forward in
web browsers and elsewhere (nautilus)... But on this fresh install of
Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
consoles (the ctrl+alt+f1 ones). But it's not listed as one of the
shortcuts in the "keyboard" menu, so I don't know how to disable it...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1700705] [NEW] pesky "ubuntu-sso-login internal error" followed cross upgrade
Public bug reported: tl;dr will I regret uninstalling ubuntu-sso-login? software-center? do you want my help debugging this?[1] I see last release was over a year ago, so I'm guessing uninstalling is fine, but please advise. I've been getting these continuous "internal error" pop-ups in ubuntu from 14.04 LTS, and now (through my upgrade to 16.04) they still popup: python traceback that ubuntu-sso-login line 39 (of twisted/__init__.py) raised the ImportError "Twisted requires zope.interface 3.6.0 or later: no module named zope.interface" apt-cache rdepends seems to suggest the only thing worth keeping 'ubuntu-sso-login' installed for is software-center package. is software-center critical to ubuntu-desktop's operation (eg: if I never open it anyway?). I've guess not, and uninstalled it (it was at 16.01+16.04.20160420 -- ie: over a year old). But please correct me if I'm wrong and I should re-install before I experience some mysterious pains later. I figure better to discuss this here than in stackexchange, or other places I see this error discussed. [1]: I mean: if you really want to fix this exception, I'm happy to walk through any debugging steps you need -- but if it's a bug that's hopeless, that's okay too. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of stacktrace from "internal error" reporter - unsure how to copy/paste its plain-text" https://bugs.launchpad.net/bugs/1700705/+attachment/4903930/+files/Screenshot%20from%202017-06-27%2003-00-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1700705 Title: pesky "ubuntu-sso-login internal error" followed cross upgrade Status in software-center package in Ubuntu: New Bug description: tl;dr will I regret uninstalling ubuntu-sso-login? software-center? do you want my help debugging this?[1] I see last release was over a year ago, so I'm guessing uninstalling is fine, but please advise. I've been getting these continuous "internal error" pop-ups in ubuntu from 14.04 LTS, and now (through my upgrade to 16.04) they still popup: python traceback that ubuntu-sso-login line 39 (of twisted/__init__.py) raised the ImportError "Twisted requires zope.interface 3.6.0 or later: no module named zope.interface" apt-cache rdepends seems to suggest the only thing worth keeping 'ubuntu-sso-login' installed for is software-center package. is software-center critical to ubuntu-desktop's operation (eg: if I never open it anyway?). I've guess not, and uninstalled it (it was at 16.01+16.04.20160420 -- ie: over a year old). But please correct me if I'm wrong and I should re-install before I experience some mysterious pains later. I figure better to discuss this here than in stackexchange, or other places I see this error discussed. [1]: I mean: if you really want to fix this exception, I'm happy to walk through any debugging steps you need -- but if it's a bug that's hopeless, that's okay too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1700705/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
(attaching alsamixer card-views, per last comment) ** Attachment added: "card-0_vs_card-1_top-vs-bottom.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748140/+files/card-0_vs_card-1_top-vs-bottom.png -- 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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
Sorry, I failed to mention in comment #9 that the actual *problem* is I no longer hear any audio, and no longer have microphone access. Another screenshot attached (of sound settings UI - upon initial installation, this was non-empty). Here's my current output for `grep "Codec:" /proc/asound/card*/codec*` /proc/asound/card0/codec#0:Codec: Intel Broadwell HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC286 (per https://wiki.ubuntu.com/Audio/HDAGeneric from https://wiki.ubuntu.com/DebuggingSoundProblems) Also, `alsamixer --card=1` shows me audio level bars. Where as `alsamixer` (default: card 0) shows me nothing~ish (zero-height bar- toggles) - also attahed screenshot ** Attachment added: "Empty gnome sound settings UI" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748139/+files/empty-sound-settings.png -- 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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
disclaimer: I'm trying to confirm if this affects me (so, please chime in if someone reading this can point me elsewhere or confirm)... I found on initial install - of Ubuntu 16.04, on Samsung ATIV 9, 12inch laptop - that audio/mic. worked perfectly without issue. Now, since multiple boots and updates, I am finding that volume up/down icon (in gnome 3's grey overlay -- attached screenshot) indicates "HDMI / DisplayPort" I *do* have a micro display port on the side of this laptop (I believe called HDMI "type d"), but I haven't once plugged into since purchasing the laptop. ** Attachment added: "Gnomeshell overlay indicating that my volume controls are interacting with "HDMI / DisplayPort"" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748138/+files/Screenshot_2016-09-24%2017-49-28_Indication-of-HDMI-port-Intercepting.png -- 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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 287215] Re: xmodmap settings not getting honored when keyboard devices are hotplugged
Can someone suggest how to fix this properly? I'm happy spend the time understanding some code and sending a patch. My reproduction: - my ~/.xprofile has the following line which turns caps into a Control_L key: `xmodmap ~/.Xmodmap`[1] - I have a bluetooth keyboard for my 14.04LTS ubuntu machine - when I walk away from the machine, I turn off my keyboard (to preserve battery/charge) - when I come back and unlock my screen, my config is reset (ignoring my previous `xmodmap` calls) Also, wow(!), the 7th anniversary of this bug is coming up :) [1]: https://github.com/jzacsh/dotfiles/blob/411572a68ead36ab240bad9e6a550188f19023d1/.config/xmodmaprc#L15-L17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/287215 Title: xmodmap settings not getting honored when keyboard devices are hotplugged Status in xorg-server package in Ubuntu: Confirmed Bug description: Binary package hint: xserver-xorg-input-evdev I use xmodmap to map the caps lock key to the meta key with the following in my ~/.Xmodmap: ! ! - map capslock to meta key ! remove Lock = Caps_Lock add Mod3 = Caps_Lock This works correctly on Intrepid on my lenovo T61's built-in keyboard. When I plug in a USB keyboard, caps lock is not mapped to meta, though it still is mapped that way on the built-in keyboard. If I then re-run xmodmap on my .Xmodmap, caps lock on the USB keyboard gets mapped correctly; however, unplugging and re plugging in the USB keyboard results in its caps lock key being reset to the unmapped state. This worked correctly on hardy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/287215/+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 1132215] Re: rhythmbox crashes when syncing library to ipod
First google result for upgrading to 13.10 (not recommended) http://askubuntu.com/questions/302762 I don't know anything about Rhythmbox's codebase... could someone list commands needed to build and run it from head? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1132215 Title: rhythmbox crashes when syncing library to ipod Status in “rhythmbox” package in Ubuntu: Fix Released Bug description: Rhythmbox crashes when I try to sync my music with my ipod 5th gen (w/ video). I'm running the development release of 13.04, looking for bugs and whatnot. I did not have this problem before with any other version of rhythmbox or Ubuntu. The error generated is: (rhythmbox:4117): GLib-GObject-WARNING **: g_object_set_valist: construct property encoding-target for object `RBTrackTransferBatch' can't be set after construction Segmentation fault (core dumped) rhythmbox 2.98-0ubuntu3 Ubuntu 13.04 raring ringtail ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Sat Feb 23 13:53:50 2013 InstallationDate: Installed on 2013-02-10 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1132215/+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
