[Bug 1730551] [NEW] Issue streaming VP9 based videos with MPV in 17.10 with VAAPI hardware accel in Wayland session
Public bug reported: Hi friends. I'd like to share some findings. These have included the 17.10 repo version of MPV (v0.26) as well as a more recent PPA version (v0.27). Behaviors have been the same between the two versions. This is using VAAPI hardware acceleration. My processor is an i5-7200u. My system is Ubuntu 17.10. I'm using the Wayland session. mpv.conf: gpu-context=wayland hwdec=vaapi vo=gpu save-position-on-quit The issue comes in when streaming certain videos online. I was finding some videos would work fine, yet others would present a lot of gray box-like artifacts, enough where visibility of the video was impossible. I began to pay more attention to the terminal output when launching mpv + youtube.com URL via CLI. After some searching about video codecs, I began to wonder if the issue was specific to VP9 videos. jason@JasT470:~$ mpv https://www.youtube.com/watch?v=V54CEElTF_U Driver 'opengl' has been replaced with 'gpu'! Driver 'opengl' has been replaced with 'gpu'! Resuming playback. This behavior can be disabled with --no-resume-playback. Loading config '/home/jason/.config/mpv/watch_later/13BA6C9FE6A59BE339409C1DB84E3403' Playing: https://www.youtube.com/watch?v=V54CEElTF_U (+) Video --vid=1 (*) (vp9 1920x1080 29.970fps) (+) Audio --aid=1 --alang=eng (*) 'DASH audio' (opus 2ch 48000Hz) (external) AO: [pulse] 48000Hz stereo 2ch float Using hardware decoding (vaapi). VO: [gpu] 1920x1080 vaapi[nv12] AV: 00:00:26 / 00:03:26 (12%) A-V: 0.000 Cache: 10s+23MB Saving state. The above resulted in video that looks like the attached image. At times the video would seemingly buffer enough and work, though most of the time it looked like that image. Even when it would clear up a little bit, any sort of seeking would instigate the gray to overtake the majority of the player window again. During this time I experienced no issues with audio when the video was playing. After doing some digging and finding some discussion regarding folks wanting to avoid VP9 (but not having much context as to why), a string to pass in mpv.conf was provided as follows: ytdl-format=bestvideo[vcodec!=?vp9]+bestaudio/best After appending this to my mpv.conf, I re-ran the same video as I did above. jason@JasT470:~$ mpv https://www.youtube.com/watch?v=V54CEElTF_U Driver 'opengl' has been replaced with 'gpu'! Driver 'opengl' has been replaced with 'gpu'! Resuming playback. This behavior can be disabled with --no-resume-playback. Loading config '/home/jason/.config/mpv/watch_later/13BA6C9FE6A59BE339409C1DB84E3403' Playing: https://www.youtube.com/watch?v=V54CEElTF_U (+) Video --vid=1 (*) (h264 1920x1080 29.970fps) (+) Audio --aid=1 --alang=eng (*) 'DASH audio' (opus 2ch 48000Hz) (external) AO: [pulse] 48000Hz stereo 2ch float Using hardware decoding (vaapi). VO: [gpu] 1920x1080 vaapi[nv12] AV: 00:00:07 / 00:03:26 (3%) A-V: 0.000 Cache: 10s+25MB Saving state. As you can see in this second output (yet sourcing the same YouTube video), h264 is used in place of VP9. In this case, I had no video artifacts whatsoever, leading me to suspect the issue may be isolated around the VP9 codec. Please let me know if I can be of any assistance with testing. Thank you for your time! ** Affects: mpv (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2017-11-04 23-48-39.png" https://bugs.launchpad.net/bugs/1730551/+attachment/5005094/+files/Screenshot%20from%202017-11-04%2023-48-39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730551 Title: Issue streaming VP9 based videos with MPV in 17.10 with VAAPI hardware accel in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1730551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
Er, it might be possible to ignore my prior post (couldn't find a means to edit it). Originally I installed the .deb via Gnome Software, but I later (after already posting my experience with the update, of course) checked the version of the package via dpkg -l. It indicated I was on 17.10.1... not .2. This time I installed the package via dpkg -l. After verifying it was 17.10.2 via dpkg -l I tested again, specifically with Dropbox and Telegram since they were issues before, and they seem to be holding on when resuming from lock screen. I can't instigate them to disappear now. Apologies about that. I'll continue testing, but so far, so good. Thanks. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
Thank you, developers, for your time regarding this issue. I'd like to chime in with my experiences following the proposed patch. Full disclosure: I did not enable proposed. I just downloaded the .deb generated for the appindicator-17.10.2.deb package and installed it. Afterwards, I rebooted and began to tinker. The appindicator seems to "mostly work", at least with the apps I tested. These apps were Telegram, Quassel-Client, Nextcloud-Client, Dropbox, and VLC. Quassel, Nextcloud, and VLC work fine. They come back each time (so far in my testing) when unlocking the screen. This success is true for both typical locks/unlocks along with suspend/resume. The only thing worth noting about this behavior is that the order of the icons seems to change every time. It's almost as if they are ordered by their response speed upon the session unlocking again. It varies, it's not a big deal, but I think it's worth noting, however they *do* come back -- that's an improvement for sure. The story changes with Telegram and Dropbox. With ease I can trigger the disappearance of the Telegram tray icon. One suspicious thing worth noting here is the Telegram tray icon is very undersized. This is entirely speculation, but is it possible Telegram is excluded from this patch working because of this undersized icon issue? I recall seeing a bug report regarding very small icons in the appindicator tray... Dropbox failed to come back approximately 3/4 of the time. On some tests, Dropbox did come back, but an easy majority of the time Dropbox was no where to be found upon resuming. I can confirm via system monitor that Dropbox is still indeed running, though. If there are other patches in proposed that might help with this, then I apologize ahead of time regarding the fact that I simply downloaded the appindicator.17.10.2.deb package from launchpad. Otherwise, while there's some definite improvements, perhaps this behavior is the sign of a lingering issue. Again, thank you devs, for your time and hard work. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719192] Re: Some Top Icons Disappear After Screen Locks - 17.10
Qt upstream report, possibly related: https://bugreports.qt.io/browse/QTBUG-63065 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719192 Title: Some Top Icons Disappear After Screen Locks - 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1719192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713712] Re: [UIFe, FFe] Provide Unity Launcher API
Question - should we see the unread message indicator, as is, right now in dock v0.6? Currently I'm logged in to Telegram on my 17.10 laptop with Telegram running. I installed the .deb for v0.6 dock: ||/ Name Version Architecture Description +++-==---= ii gnome-shell-ex 0.6 all Ubuntu Dock for GNOME Shell I have a desktop system, Ubuntu 16.04 with Unity, off to the side also running Telegram. The laptop (Ubuntu 17.10) does not display the unread count indicator on the Telegram icon within the dock. The desktop (Ubuntu 16.04) however does. Telegram is fully up to date on both systems, and both systems are fully up to date. I need to test more applications but I kept hearing that Telegram should be supported, however I'm not seeing any indication it is on 17.17 + v0.6 of the Ubuntu Dock. Can anybody else confirm their findings? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713712 Title: [UIFe, FFe] Provide Unity Launcher API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1713712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719192] [NEW] Some Top Icons Disappear After Screen Locks - 17.10
Public bug reported: Hi friends. I'm testing Ubuntu 17.10 with Gnome 3.26. I noticed some top bar icons disappear after my screen locks and I go back in to my active session. As an example, I currently have Quassel, Telegram, and Nextcloud sync client in the upper right corner displaying their task tray icons. If I lock my screen and re-authenticate back in to my active session, Quassel remains, but Telegram and Nextcloud are gone. The only way to get them back is by closing the application the missing icon belongs to and re-launching it. Thanks for all of your hard work! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 24 10:57:24 2017 InstallationDate: Installed on 2017-09-01 (23 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170830) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719192 Title: Some Top Icons Disappear After Screen Locks - 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1719192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Same deal here on 4.8.0-34-generic with 16.04. Just got a Bluetooth headset hoping they were less terrible than they were years ago. I was excited that it worked well, sounded great, etc., but here we are with the operating system being the one with issues. I tried the workarounds above. Once the issue comes up I can switch to the headset mode without issue, however switching back to high fidelity playback fails. It doesn't error out, but it will automatically switch to my laptop speakers despite the fact I specifically chose high fidelity mode on the bluetooth headset. In my experience, it's not difficult to instigate this issue. I've had it happen a half dozen times in the 30-40 minutes that I've been working with these headphones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]
I installed 4.8 hwe edge from the repositories on my 16.04 system (Macbook Pro with Broadcom 4331 card). I lost wireless. I rebooted, made sure I was up to date, etc etc. Nothing in 4.8 would work. Anything 4.4.x would work fine though. I received an error when installing via terminal much like the error in the original post. This gave me a lead which ultimately lead me here. Installing via GUI (system settings >> software and updates >> additional drivers) did not yield any sort of error. In the end, nothing worked with getting wifi working again on 16.04.1 + BCM4331 + HWE Edge Kernel 4.8 -- until I downloaded the .deb Vincent linked in post 14 above. I was skeptical to try it as the version numbers of the .deb seemed to match what was in the repos when I searched Synaptic, but alas, I tried it. Immediately I reconnected to wifi on my 5ghz network. I installed it via dpkg -i in terminal, and the output looked cleaner. Given I tried installing the 4.8 hwe edge kernel here on February 2nd and ran into this problem... yet 16.04.2 is due out within days... I raise the difficult question and can't help but to wonder if things are "ready". Otherwise I would anticipate an additional flurry of reported issues coming in relating to this topic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595765 Title: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655099] [NEW] Feature Request - Scale/Zoom Features for Visually Impaired
Public bug reported: Hi friends. I'm submitting this bug/feature-request in an effort to voice support behind any and all current visually accessible features, including but not limited to: Display Scaling, Desktop Zoom with keyboard toggle, and High Contrast Text. I work for a public school district with a lot of Ubuntu machines in use on a daily basis. These features, and I cannot stress this enough, are critical to these kids who rely on it to enhance their computing experience in class. Once some simple settings are toggled (whether in the current System Settings or something like Unity Tweak Tool), it's been pretty incredible to see students give you the nod that "I got it from here" and continue onward with their learning. I'm sure it would benefit a multitude of other folks of any age range as well who fit this paradigm of being able to utilize these visually assisted features. The current Unity 7 does an excellent job of this. Similar capability in Unity 8 would simply be a gold set of features to have. Thank you for your time, consideration, and continued hard work! ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655099 Title: Feature Request - Scale/Zoom Features for Visually Impaired To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1655099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
I'm surprised this is still a thing. I added the common systemd "restart network-manager on resume" script most folks with this issue have used. I added it quite a while ago. My system has been working consistently since then without issue... to the point I actually forgot that this bug existed. I understand the burning desire to fix the problem at hand, but months (soon to be a year) later, this issue still exists. I don't see the trade-off/downsides/consequences with this work-around being applied. If a downside does exist, I haven't seen it, but what I have seen is the benefit of it being in place as it circumvents this issue entirely. Sorry - I just don't see the point of this bug trailing on longer and longer while users unaware of the "restart network-manager on resume" fix continue to deal with the headache, while on the other hand, had that work-around been issued, folks wouldn't be as angry about this issue as they clearly are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624181] [NEW] A proposal to improve the behavior of the notification system.
Public bug reported: Hello friends. I'm writing this message as a proposal in regard to the way notifications work in Ubuntu. For several years (I wish I wasn't exaggerating there) I've noticed odd times where my notifications seemingly did not work. I had difficulty isolating exactly when this would happen. Given my work flow, I suppose it was difficult to identify the pattern. Only recently I learned something and it all made sense: Ubuntu notifications of the "normal" urgency do not work when videos, such as local videos or YouTube, are currently playing. For all but a minute, I was relieved, as I had finally understood out the pattern. I never saw this documented elsewhere or spoken about. Once that settled in I began finding myself somewhat disinterested in the predictive behavior of the notification system. It doesn't take long to identify a massive flaw in this design. Take for example a desktop with dual screen, or even a laptop with a second monitor attached. Many people are multitaskers. Earlier today I had a video playing on my 2nd monitor. Somewhat ironically, it was an Ubuntu video podcast. Because of the simple act of playing a video, I received no notifications in that frame of time. I was actively working. I was constantly watching my screen. I was doing things. The video was not my primary means of computer usage at this point in time, however because of the design of the notification system, it dictated that my notifications be silenced -- yet I was there. I was working. Those were notifications that were needed. I can list countless other examples. Rather frequently I find myself letting a YouTube music stream run, containing 3 hours of background music while I worked. There was no video, but because it was YouTube, notifications were silenced as per the guidelines of the notification system. Other times I may find myself playing a live concert, or a video with stand up comedy, etc. I know I'm not alone with this. For people that actually depend on notifications, it's an easy majority that would prefer this behavior didn't occur like this. Upon tinkering with other distributions more, namely Gnome based distributions as well as elementary Loki, I realized just how much more logical other approaches are to the notification system. This assumed behavior dictating what notification displays on the screen versus which don't based on system processes is not helpful. It's obstructive to the user experience, whether that be their work flow at their day job or personal time on their computer. It casts more questions and frustration than assistance. The ability to silence your notifications via a simple drop-down slider is absolutely brilliant. It puts the power of the notifications in the hands of the user via one, single, simple click. Likewise, these other systems provide a history of notifications. The act of walking away from my computer for all but 30 seconds can mean a missed notification. I don't mean missed as in, "oh darn I didn't see it", but I mean missed as in... it's simply *gone*. There is no history. There is no retrieval. There are no means available to see what transpired in that 30 second window. Meanwhile, on other platforms, I walk away and look away from my screen with an odd sense of confidence knowing for an absolute fact that whatever may happen that requires my attention will certainly get my attention upon my return. With Ubuntu's current behavior, it's a simple coin toss. If you're there at the time, and of course not playing any YouTube music, a local video, or anything else of that capacity, you can actually see what happens thanks to the notification system. With videos playing on a second monitor or a YouTube music track in the background, it's simply "tough luck." This proposal is an attempt to encourage developers to strongly consider altering this behavior. The current state of the notification system simply feels like it was designed for a C+ grade, and stopped short of an otherwise instant home-run. This degree of integration in other environments really, really shines. Sadly, it makes Ubuntu look a bit subpar in comparison. It pains me to say that, though the simple fact remains -- I am not alone. In fact, it's a considerably popular opinion that many others share. I hope that this information provided an insightful look into the usability of a user -- one who uses Ubuntu, thoroughly enjoys it, and wants it to improve in any way possible. Thank you for your time, patience, and consideration. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: notify-osd 0.9.35+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 15 21:46:52 2016 DesktopSession: 'ubuntu' GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2015-09-17 (364 days ago) I
[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
I noticed that NM 1.2.2 hit proposed yesterday. I pulled down proposed but did not see a change with NM 1.2.2 (i.e. I was still seeing the issue), though after re-reading Aron's message, it sounds like the fix is not 1.2.2, but the fix can be applied to 1.2.2 once it becomes available. Anyway, after this I added the testing PPA fourdollars provided to my main laptop (1 of 5 wireless devices I have that are seeing this issue). I've had it running for the last day or so. As of now I have not seen the issue come up after adding the PPA. Whatever was changed in the PPA (which I can't lie, I'm rather curious to know) seems to have done the trick. While I could instigate the wireless issue before by closing/opening my laptop lid only a few times (this issue was a quite simple roll of the dice, not difficult to notice, further confusing me as to why it wasn't tackled before release but that's another conversation), the real culprit that seemed to always cause it was when my laptop was suspended for several hours. Even after an all-night suspend, the laptop resumed from suspend without issue and connected to wifi this morning. Thank you folks for the testing PPA. Fingers crossed this issue can be fixed soon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
Christian - Agreed. This should be a higher priority bug given it directly abstructs workflow. I don't know how many times I've been moving along with a ton of things open only to realize I need to pull in an application, but oh wait, I need to log out and back in in order to access it. Sometimes that's just not feasible. I've also noticed it's not always consistent. I have installed applications that do show up, but more times than not, the newly installed applications simply don't show until I log out/back in. I don't recall seeing this on prior versions of Ubuntu. In my experience it only surfaced with the introduction of 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1506744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
Same deal here. Installed gimp via apt-get in terminal, nothing in dash. Uninstalled + purged it, reinstalled through software center, same thing -- no results found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1506744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442005] Re: Notifications are shown forever
Just discovered this myself tonight. Running 15.04 on multiple machines -- same issue with Quassel on all machines I tinkered with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442005 Title: Notifications are shown forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1442005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1497366] [NEW] System tray/top panel on 2nd monitor flashes with dash activated on primary monitor.
Public bug reported: Hello friends. I stumbled across a graphical issue that I wanted to report. I was able to duplicate this on Ubuntu 14.04.3 LTS as well as Ubuntu 15.04 with all of the updates done on both systems as of today. Both systems also vary quite a bit in hardware (l14.04.3 system = Latitude 7440 laptop with Intel graphics, 15.04 system = desktop with Intel CPU and Nvidia 9600GT/Nouveau drivers). I created a screencast of the issue happening. Please note this screencast is of my 2nd monitor only. To reproduce (which can sometimes be a little inconsistent, though a matter of 60 seconds I was able to replicate it -- then once it happens it seems hard to ignore), have a couple windows on each monitor. In my case, I felt as though I noticed the issue more frequently with Firefox, though I did replicate it with Libre Office as well. Click on the 2nd display to activate it as the active monitor. Move the cursor to the 1st monitor, but do not click anywhere. Press the super key to activate the dash. That's it. The dash seems to follow the cursor and open on the monitor the cursor resides in, regardless of where you last clicked. With the second monitor "active" (via a prior click) but the dash opening on the first monitor via keyboard shortcut, it seems to instigate the issue. Pending that you have a few windows open, it won't take long to replicate what you see in the video. In the video, all I did on the 1st display (what's not seen) is move the cursor to that monitor and press the super key. https://www.dropbox.com/s/vr0k0qp1l01bxz4/Ubuntu-Flashing-2nd- Screen.mp4?dl=0 Thank you for your hard work, time, and energy! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 18 12:21:21 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Subsystem: ASRock Incorporation Device [1849:0102] NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0545] InstallationDate: Installed on 2015-09-17 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=c25681e4-6e30-4021-ab9f-8937d41d8017 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: H61M/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd04/10/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Sep 18 12:19:00 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech K270KEYBOARD, id 9 inputLogitech M185MOUSE, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau ** Affects: unity (Ubuntu) Importance: Undecided Status: New **
[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work
Same issue here. Doesn't seem fixed. I have the same issue with other Ctrl related shortcuts, like my custom shortcuts Ctrl Alt 7, Ctrl Alt 8, etc. Logging out and back in fixes it but that's hardly a suitable workaround when the missing shortcuts are only realized after you're already neck deep in work. It just seems tied to that Ctrl key, Ctrl Alt T included with terminal, though certain shortcuts are seemingly exempt, such as window management shortcuts, I.e. Ctrl Super left/right arrow or Ctrl Alt up/down arrow, etc. 14.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453223] [NEW] Traceback error when opening system-config-samba; no such file/dir: /etc/libuser.conf
Public bug reported: Ubuntu 15.04. Fully updated as of this writing. I installed system- config-samba from the repos to manage some samba shares. Upon installation, the "Samba" application icon never appears in the list of applications in the dash. I did however attempt to launch it via terminal as root, but what I got was this. root@JSZ835:/etc# system-config-samba Traceback (most recent call last): File "/usr/sbin/system-config-samba", line 45, in mainWindow.MainWindow(debug_flag) File "/usr/share/system-config-samba/mainWindow.py", line 121, in __init__ self.basic_preferences_win = basicPreferencesWin.BasicPreferencesWin(self, self.xml, self.samba_data, self.samba_backend, self.main_window) File "/usr/share/system-config-samba/basicPreferencesWin.py", line 97, in __init__ self.admin = libuser.admin() SystemError: could not open configuration file `/etc/libuser.conf': No such file or directory If I run "touch /etc/libuser.conf", then re-run system-config-samba as the root user, it opens the interface. Even afterwards, the application icon is no where to be found in the dash. I also noticed the desktop file had this entry: Exec=gksu system-config- samba However, gksu is seemingly not installed by default on 15.04. Thank you for your hard work, dedication, and time! Have a great day. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: system-config-samba 1.2.63-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 8 13:22:37 2015 InstallationDate: Installed on 2015-04-21 (17 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150417.1) PackageArchitecture: all SourcePackage: system-config-samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: system-config-samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453223 Title: Traceback error when opening system-config-samba; no such file/dir: /etc/libuser.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-samba/+bug/1453223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427942] Re: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work.
Hi there Christopher. I tried 3.13.10 and I didn't have any issues. I was able to suspend (on lid close) and resume a dozen times in a row. Back on 3.19.0.15, it oddly has suspended, but I have difficulty replicating it. For example, on a fresh boot I suspended on lid close once. But then I resumed and tried again, and it just sat there running. It seems a bit inconsistent with what I am seeing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427942 Title: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427942] Re: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work.
Hi there, Christopher. I just tried that kernel. It's reading as: 4.0.0-04rc4-generic via uname -r. Same deal in this case as before. Suspend on lid close does not work, but selecting suspend from the gear menu in the upper right successfully suspends the laptop. Thanks for your quick insight! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427942 Title: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427942] Re: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work.
I installed today's daily build of 15.04. Following the install, I did a complete dist-upgrade. I pulled in kernel 3.14 as well as 4.0 from the following sources. 3.14 = http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.4-utopic/ 4.0 = http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ In all cases, with 3.14 and 4.0 listed above, as well as 3.19 out the out of the box 15.04 install, suspend on lid close did *not* work. Again, in all cases, selecting suspend from the gear menu in the upper right successfully suspended. I did verify my settings within System Settings >> Power that "suspend on lid close" was selected. A reminder that 14.04.2 was flawless in this regard. I have not tested 14.10, but I can if it would serve value to this bug report. Thanks for everything! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427942 Title: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
I couldn't see an obvious way to edit my above post, so apologies for sending out a second comment, but I do have to ask... why would the default parameter for focus-prevention-level not be 0 anyways? It doesn't seem, do I dare say, all that logical to have it set to 1 since it only ends up providing inconsistent behavior with the way things from system tray open. It being set to 0 provides that consistency. It would surely remove the "look on your launcher, see? it's there after all" comments I have to make quite often so users know that the application they tried to open from system tray isn't broken, it indeed launched, it's just... minimized and in your left launcher. Thanks for all of your work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
Running 14.04.2 here with some of the same issues. I was seeing it with ownCloud client, network manager, and a weather applet known as my- weather-indicator. The issue came up at random, but it was easy to replicate within a matter of 15-20 seconds while continuously navigating around open windows followed by opening applications with system tray icons. I brought up conversation with some other users who gave me a suggestion that has, so far, worked. Figured I'd post it here in case it can benefit anybody else until the bug can be properly fixed. I ran this in terminal, followed by a log out/log in. dconf write /org/compiz/profiles/unity/plugins/core/focus-prevention- level 0 This is a similar idea that Rael posted in response 43 above. I seem to recall Ubuntu switching to dconf over gconf at some point. I tested it in my 14.04.2 virtual machine (brand new, but fully updated install) however the gconf key didn't appear to fix the issue, as I was still able to replicate it. In the same VM, that dconf write command above seemed to fix the issue, as I have been unable to replicate it in my VM, nor my main laptop. The default focus-prevention-level is 1, which is considered "low", but appears to be the cause of this random behavior. Setting it to 0 seems to make it consistent. I haven't ran with this change for days/weeks/months, but in my tinkering so far today, the issue hasn't resurfaced a single time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427942] Re: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work.
I'll swap out to my other SSD later and spin up 15.04 again to test. Though for now it might be worth mentioning that I did install Manjaro Linux on a 2nd partition to tinker with some newer packages with the AUR. It's on kernel 3.16, and like i said, different partition but same laptop. I closed the lid and it did absolutely nothing, even though it was set to suspend on lid close. That makes me feel somewhat confident that this might be an upstream kernel issue. Traditionally this laptop hasn't been great with this kind of stuff. Even today, assuming suspend/resume *does* work, the brightness controls via the Fn keys have never worked after a resume. But on a fresh boot, Fn keys to control brightness are just fine. I'll still test 15.04 again for further confirmation before I report anything upstream, but my gut thinks the writing is on the wall. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427942 Title: [Toshiba Portege Z835-P370] 15.04 Beta suspend on lid close does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427942] [NEW] 15.04 Beta, Toshiba Z835, suspend on lid close does not work.
Public bug reported: Hello friends. I fired up 15.04 beta on my Toshiba Z835 ultrabook. Upon lid close, the system does not suspend despite being set to suspend on lid close for both battery and on AC power. This worked fine under 14.04, however I admittedly never tested 14.10. If I select the gear in the upper right corner and hit suspend, it suspends and even resumes fine. Also worth mentioning is a long standing issue with the Toshiba Z835, where following resume from suspend, the function keys which control the brightness no longer work. I see the meter go up and down, but it doesn't change the actual brightness. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: boot/vmlinuz-3.19.0-7-generic] ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2130 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 3 20:40:39 2015 InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150303) MachineType: TOSHIBA PORTEGE Z835 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=4bf1f853-b598-4a66-874b-8a41c88f3de1 ro quiet splash vt.handoff=7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.80 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427942 Title: 15.04 Beta, Toshiba Z835, suspend on lid close does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919801] Re: Unity dash file search is extremely slow
I just experienced some monumental slowness on my work laptop, which is a Latitude E7440 that came with Ubuntu on it from Dell. Intel i5, 8GB RAM, SSD, and still I felt like I was on a Pentium 4 rig. The slowness got worse over time, but I did my best to ignore it. I just didn't understand how my laptop was running so bad when a Pentium Dual Core system I have at home on a spinning hard drive was wildly faster with the same installation of 14.04 with the same flash drive/ISO. Reading through the above responses some users talked about removing the old zeitgeist database, which would force zeitgeist to rebuild a new one. Someone mentioned that they noticed a speed improvement when removing their ~180 MB instance of zeitgeist. I checked mine... 1.3 GB! Yes, 1.3 GB was tied up with zeitgeist. While I do use my laptop all throughout my work day, every day, it still surprised me as I haven't even had it for a full year yet. This is a bit concerning, as it feels somewhat inevitable that users will face a slow down over time - it just depends on your usability, as you may never see it or it may be far enough into the future where you likely already rebuilt your system on a newer install. That said, I removed all of the files in there and boom. Much, much better. While my initial database size was in the kilobytes, once I rebooted it came up to about 48 MB. It's sitting now at 50.0 MB and hasn't risen at all (yet) despite me searching for multiple folders, files, and applications in the dash itself. I'm hoping it's quite a long time before I see zeitgeist hitting the gigabyte mark again... Clearing this out made Unity significantly faster to work with. It, honestly, restored a lot of my joy with using Unity. This process felt similar to nuking the cache in a web browser. Just to fire out some thoughts in case they are of any assistance with generating ideas, perhaps there's a way within the zeitgeist sqlite database to automatically purge older items once the database hits its cap size. Let's say we set the cap at (pulling a random number out here) 100 MB. Once we roll over to 101 MB, the data in the initial 1 MB slice would get purged. Sort of like a logrotate setup. Or, of course, it could auto purge once a week on an anacron basis. That might be acceptable as well. (from an end user point of view, either way would be acceptable, but I'm not sure what technicalities exist that would dictate one choice over the other). Either way, there's no reason to have end users worrying about purging the database Unity relies on. Without this workaround, users experiencing Unity slowness are simply stuck with a slow Unity interface. This surely is not a preferred experience by any stretch. Unity 7 is not going anywhere as per Canonical's decision to have Unity 7 defaulted on the next few short term releases, including the current already-released 14.04 LTS. As a result, (I cannot emphasize this enough), I hope this isn't a "wait for Unity 8" type of solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919801 Title: Unity dash file search is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-files/+bug/919801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
@ Emmanuel Not to sound pessimistic, but there seems to be a rather wild different between one 7260 to the next 7260. Myself and two co-workers got the same XPS 13 with Ubuntu. The other two had no issues, while I would disconnect continuously, often times even when we were in the same room. We were running the same distro and everything. Even when I swapped the card three times, antenna twice, and the motherboard once, the issue persisted. Ultimately this resulted in me trading up the XPS 13 under warranty for a Latitude E7440 with Ubuntu, so it worked out (for me) despite the issue not having been "fixed". Likewise, a friend of mine had a laptop with a 7260 chip where he had nothing but issues despite the extensive amount of troubleshooting and testing he did. He ended up buying another 7260 based laptop ready to swap the chip but he ended up having no issues, so he just kept chugging along with it. There's a massive thread on the Intel forums with seemingly no answer. Users from all types of distributions and operating systems are posting about their issues, from 7 to 8 to Arch and Ubuntu. I want this fixed in ways I cannot begin to describe, but we're about 1.5 years in since this card's release with no "official" fix, just odds and ends tweaks that seem to help one or two users, but not everybody. I can't help but to feel that this is some sort of hardware issue. Unfortunately, Intel has been rather quiet about it, so at this point it's nothing more than an assumption. Anyway, just wanted to throw that out there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330405] Re: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear.
Same deal here. 14.04.1, fully updated, etc. Running on a Dell Latitude E7440 that even came with Ubuntu on it. If I plug in a second display after the system is booted, the top panel on the secondary monitor goes transparent. If I boot the system up with the monitor plugged in, no issue. If I issue a restart to unity (ALT + F2, unity --replace), then it comes back fine. This does not happen if your panel is default transparency, though it does happen if the transparency of the panel has been adjusted (at least in my experience). ** Attachment added: "dualscreen2.png" https://bugs.launchpad.net/unity/+bug/1330405/+attachment/4298631/+files/dualscreen2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330405 Title: Unity top panel turns transparent with dual screen. Garbage shadow leftovers appear. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
It sounds like the 7260 wireless card is an all around headache for pretty much any operating system. To date I have heard of a great deal of users with issues on Windows 7, 8, 8.1, Ubuntu, Mint, Fedora, Arch, and Debian. Perhaps others, but those are the specific ones I recall. There's a lengthy discussion on the Intel forums... not that it helps out much for this specific issue, but I figured it's worth mentioning that we (us Linux users) are not alone with 7260 woes. https://communities.intel.com/thread/47983?start=0&tstart=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume
Thanks for the tip, Phasmus. Killing the process on 14.04 seems to help my issue as well. Otherwise Empathy is downright unusable given its wildly inconsistent behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk "Requires Authorization" after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340477] Re: The HUD doesn't support scaling on HiDPI monitors
Hello there. I use 14.04 on my HTPC as a Netflix (Chrome) and XBMC system (which works exceptionally well might I add). Due to it being a home theatre system, I ramp up the display scaling quite a lot (2.0). I noticed the HUD did not compliment display scaling, as mentioned in the bug report above. To date, this system has only been a regular, vanilla 14.04 instance with whatever updates that come down the main pipe. After finding this bug report, I enabled -proposed and did a full apt- get update and apt-get dist-upgrade. I pulled down Unity 7.2.3. Not only does the HUD now compliment the display scaling, but my mouse cursor is also adequately sized as well. Upon initial use, I have found no regressions or issues to report, however I admit I've only been booted into the system for a few moments following the update to 7.2.3. Given the HTPC gets a decent amount of use as we have no cable TV, I'll bookmark this report and comment if I run in to anything else. Thank you for your hard work, dedication, and time. It's appreciated by us users! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340477 Title: The HUD doesn't support scaling on HiDPI monitors To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1340477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319542] Re: Unity urgent animation needs an adjustable time length.
Nothing like having a message waiting for 2 hours because I missed the sound and it did not re-wiggle to catch my attention. This... this is needed. It's a must-have feature. Every other OS has something like this in place, even some other desktop environments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319542 Title: Unity urgent animation needs an adjustable time length. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1319542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361644] [NEW] 14.04. Resume from suspend with HDMI display, login/lock screen freezes.
Public bug reported: Hello friends. I have a Dell Latitude E7440 that came with Ubuntu on it. I am running 14.04.1 with all available updates as of today. I noticed if my laptop is in suspend mode and I plug in an HDMI monitor, then open the lid to resume, it freezes. The lock screen allows me to move my cursor around, but I cannot click anything, and the keyboard itself does not respond whatsoever. If I do these steps in any sort of different order, as in resume laptop first then plug in, etc., it's fine. It's just when the system is resuming with a new HDMI source plugged in that wasn't there when it went to sleep. Thank you for your time, dedication, and hard work! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 2108 F pulseaudio /dev/snd/controlC0: jason 2108 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 26 08:51:55 2014 HibernationDevice: RESUME=UUID=03cfd499-6835-4cd2-a5c7-563637a29192 InstallationDate: Installed on 2014-05-28 (89 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E7440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=e9072d7d-fbef-4b02-b325-ca00890c8aa4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PC4X0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0PC4X0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361644 Title: 14.04. Resume from suspend with HDMI display, login/lock screen freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1361644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261668] Re: Intel 7260 firmware causes crashes, needs updating
*** This bug is a duplicate of bug 1265436 *** https://bugs.launchpad.net/bugs/1265436 This wireless card is extremely problematic on any operating system. Users from Windows 7, 8, 8.1, BSD, Arch, Gentoo, Ubuntu have all reported the exact same issue. A quick Google search of this card reveals a world of complaints that makes me truly question why companies are *still* shipping it... System76, Dell, Lenovo, WHY ship a problematic card? I called Intel about my frequent disconnects on my XPS 13 Ubuntu Dev Edition, and Intel confirmed it is a known problem and they are working for a fix. (though they've been working on a fix since this chip came out a year ago with no substantial headway yet, so...). Given the length of time this chip has been out with no actual fix, I'm likely going to be stuck with swapping out my XPS with a non-7260 unit as per Dell, as Dell has no other M.2 form factor wireless cards to swap with, so that's all they could offer. I have tried Intel's latest firmware at the time of this post and can confirm it yielded no difference in results. I still disconnect at random across the 5 wireless networks I tested with different encryption levels. Sometimes it's once every 3 days (no big deal), other times a dozen times in 20 minutes (major deal breaker). It's wildly sporadic. There was a lengthy bug report that was just split off to a new report to centralize around these issues. Perhaps you can read it over and see if this applies to you. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349572 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261668 Title: Intel 7260 firmware causes crashes, needs updating To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1261668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Eh, that'd be something different then... Unless Meraki, Linksys, Dlink, Netgear, and Aruba all have the same bug in their APs. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Thanks, Seth. I wasn't necessarily suggesting that the to-be-filed bug is a 'dup', but moreso just acknowledging the fact that a lot of users as mentioned above still have problems. If these users don't have a direct link to click on the new report, subscribe and mark as 'affects me too', then the alternative is to dig around Launchpad in order to find the new bug. I was moreso just suggesting an easier way for the users above to track down and follow the new bug, that's all. :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Would it be okay to have the new bug linked here? (as in, this bug is fixed but if you're still having problems follow bug #12345678?) I'd like to be the one to report the bug, but given that I'm on the brink of swapping this laptop with another XPS 13 from Dell that doesn't have the problematic 7260 chip (sorry, but with no anticipation of a quick fix and given this is my work laptop, I have little choice), I likely won't be of additional troubleshooting assistance in a matter of a week. I would still like to follow the bug though, as I'm sure most users subscribed to this bug would as it seems the majority of users are still affected... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
3.13.0-32-generic [52184.190874] iwlwifi :02:00.0: Loaded firmware version: 22.24.8.0 I just checked and I have no updates available. In other news I let my laptop run idle throughout last night pinging a weather site every 5 seconds. I didn't drop connection once. I'm going to use the laptop throughout today and see if it comes up again. What do I do to fall back to -7? Just delete the -8 file as (I believe) mentioned above? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
Well, that's disappointing. As per the dmesg, I am indeed running 22.24.8.0, fully updated, and I lost wireless in an hour's time. This bug is not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012204] Re: Is not clear enough when an application has information or not
Not sure why this is listed as incomplete, but surely this is something that should be addressed as it's a bit inconsistent from an aesthetics standpoint. It's the little things that matter, and having the colors too closely matched is absolutely not acceptable by the vast majority of users out there. It's just too similar to tell apart. There needs to be a way to quickly and easily identify the application that needs attention. For an idea, check out elementary OS. Their "pip" dots on their dock turn a bright red. Very easy to tell apart. Light sky blue and white, not so much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012204 Title: Is not clear enough when an application has information or not To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1012204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319542] Re: Unity urgent animation needs an adjustable time length.
Any update on this, or perhaps some insight from devs about the idea? I am seeing a substantial number of users on search results indicating that they've been wanting something like this for a long time. The current setup just leaves the door open far too wide for applications needing attention to go missed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319542 Title: Unity urgent animation needs an adjustable time length. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1319542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
I just ran sha1sum against the download in that link above as well as the 7260 8.ucode that is currently in /lib/firmware and confirm they match. It seems as if I am indeed running the latest patch that is in proposed after all. As a result, something is still wildly wrong, or else I did something wrong... and believe me I'd rather know I goofed than know that this bug is still not fixed, so by all means fire away if you think I goofed somewhere. But all I can say is this very laptop is the only one with continual disconnects while everything else works flawlessly. What's funny is for several days I had no issues at home whatsoever. I had actually forgotten that this was even a problem until I suddenly couldn't get any work done or transfer anything of significant size (200 MB+) from my server without the connection tanking altogether. P.S. - As I went to hit "post comment" as I got done typing this message I lost connection yet again. I then ran a cat against syslog and copied everything over the last few minutes into a pastebin in case it helps. http://paste.ubuntu.com/7828318/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
@ Jason Gerard DeRose Thanks for your tip, but I'm a little confused. I ran grep before I downloaded/extracted anything as you recommended above, and I got: jason@JSXPS:~$ dmesg | grep iwlwifi [4.927130] iwlwifi :02:00.0: irq 60 for MSI/MSI-X [5.010242] iwlwifi :02:00.0: loaded firmware version 22.24.8.0 op_mode iwlmvm [5.082853] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [5.083253] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [5.083514] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [5.862187] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [5.862437] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 945.229994] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 945.230254] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 1720.447091] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 1720.447348] iwlwifi :02:00.0: L1 Enabled; Disabling L0S Does the line "[5.010242] iwlwifi :02:00.0: loaded firmware version 22.24.8.0 op_mode iwlmvm" not indicate that I am on the newer firmware? I came back here after I started having issues here at home. I must have disconnected from my home router six times this evening while I'm sitting across the room from it. I had proposed enabled so I could pull down Unity 7.2.2 for an unrelated bug test, so that line with the 8 entry makes me wonder if I got the update without realizing it. What concerns me is if I *did* get the update, then this clearly is not fixed... since, after all, if it were fixed I wouldn't have lost connection so many times tonight (I tested other laptops and had no issue. In one instance, my laptop disconnected while others were all connected and actively pulling large ISO files wirelessly from my file server). Sadly, I even just now lost wireless again as I was typing this... Before I begin tinkering with switching this or that I wanted to get some confirmation here by the folks who clearly know more so I can be accurate with what I'm doing. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344102] [NEW] Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't.
Public bug reported: This one seems easy to duplicate. In a dual screen setup, do the following. Place an instant message (Pidgin, etc) on monitor 1, workspace 3. Place Firefox on monitor 2, workspace 1. Have the user in the message send you a link. When you click the link, it opens in Firefox in workspace 1 as expected, but Firefox is moved from monitor 2 to monitor 1. This type of behavior should not take place as windows in other workspaces should not be shuffled around. Users place certain windows in certain workspaces for a multitude of reasons. While workspaces are great to have, behavior like this tends to be a bit of a buzzkill when users must place everything back to where it should have been in the first place. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jul 18 11:50:37 2014 DistUpgraded: 2014-04-17 17:35:16,276 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0545] InstallationDate: Installed on 2014-02-03 (164 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e0b59d9e-7632-4d75-9d1e-bbf60635a168 ro quiet splash nomdmonddf nomdmonisw SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-17 (91 days ago) dmi.bios.date: 08/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H61M/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd08/31/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jul 18 10:39:01 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344102 Title: Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1344102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344102] Re: Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't.
Note: Should have tested this prior to submitting the report, but it was an afterthought. This does not take place in Chrome. Just Firefox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344102 Title: Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1344102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1344093] [NEW] Empathy unable to open instant message to a specific contact.
Public bug reported: I am using Empathy with Google Talk under Ubuntu 14.04. With one specific contact I cannot open the instant message. I can double click all day or simply highlight them and hit enter, but nothing works. Other contacts however open up right away. The user in question that I was trying to message later informed me that he had the same thing happen. In his case, the instant message was in another workspace. It seems as if Empathy and/or Unity is not respecting the different workspaces in this case, as clicking on the name should redirect you to the workspace in which the instant message resides. In my testing just prior to submitting this bug report, I had nothing on other workspaces, and I STILL was unable to message this person. This morning was a fresh boot of my system, and I had not touched workspaces since, so anything that was hung up should have been cleared if it was workspace related. Interestingly enough, as I had the entirety of this bug report typed out and I was about to hit submit, I decided to delete my Google account and re-add it. Unfortunately, this is a common occurrence with Empathy for other reasons, but I did so again just now, and clicking the contact in question as notated above now works. What is it that is continually breaking that requires users to consistently remove and re-add their accounts to maintain connectivity/messaging functionality? As of now, Empathy is not able to 'function' so I have to use other messaging applications, but I would be more than happy to test anything necessary. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 18 11:36:50 2014 InstallationDate: Installed on 2014-02-03 (164 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: empathy UpgradeStatus: Upgraded to trusty on 2014-04-17 (91 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1344093 Title: Empathy unable to open instant message to a specific contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1344093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304186] Re: 14.04 Unity integration with messaging applications not fully working.
Any news on this? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304186 Title: 14.04 Unity integration with messaging applications not fully working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293569] Re: iwlwifi-7260-8.ucode causes network disconnections problems
I mirror Mike's question. As far as I can understand, I'm on the 7 firmware and fully updated as of today July 2nd. Yet I've had about 12 disconnects today, two of which took place as I read through this lengthy bug report. jason@JSXPS:~$ dmesg | grep "iwlwifi .* loaded firmware version" [4.427618] iwlwifi :02:00.0: loaded firmware version 22.1.7.0 op_mode iwlmvm jason@JSXPS:~$ uname -r 3.13.0-30-generic Running a one month old Dell XPS 13 with Ubuntu 14.04. Was this fixed and released and I somehow missed it via Software Updater? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293569 Title: iwlwifi-7260-8.ucode causes network disconnections problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326177] [NEW] Unable to move window to workspace via right click title bar
Public bug reported: I'm finding that I am unable to move a full screened window to another workspace. It's easy to duplicate. Simply full screen a window in another workspace, right click the title bar, and try sending it to another work space. In some cases it works. I find that moving to workspace 'down' often works. Moving to workspace left/right/up is more of an issue. I duplicated this on two different laptops on 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jun 3 19:48:24 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-05-28 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=e9072d7d-fbef-4b02-b325-ca00890c8aa4 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0D13CK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CK:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jun 3 00:07:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326177 Title: Unable to move window to workspace via right click title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1326177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283775] Re: Launcher: icon pips are not always updated properly
I don't mean to turn the bug tracker into a Q&A session, but I am curious... is that to say that this fix will be in Unity 7.2.1 and Unity 7.2.1 will land as part of the next SRU? Do SRU's land on a consistent or scheduled basis (i.e. is this another term for say 14.04.1, 14.04.2, etc) or just as soon as logically possible to address certain issues? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283775 Title: Launcher: icon pips are not always updated properly To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319542] Re: Unity urgent animation needs an adjustable time length.
Just tested the behavior with the launcher on auto hide. It looks like the icon semi pops up (about 50% of it) from the side of the screen with a wiggle, then disappears again. It continually comes up every 60 seconds after that UNTIL you reveal the launcher. When you reveal the launcher, it wiggles and stays highlighted. If you ignore it and go back about your business, the launcher hides again and the icon never does the reveal/wiggle again. Each time you reveal it, the ignored application icon is still highlighted to signify it needs attention. Even this I don't consider to be perfect. This is just my 2c here, but here's what I consider to be a perfect Unity world in regard to alerting users of applications that need attention. Auto Hide Mode: It's 99% there, but I believe the icon should still wiggle each time the launcher is revealed. Given that the highlighted backgrounds are hardly an obvious way to identify that an application needs attention, some sort of motion based animation is perfect. I also don't feel as though 60 seconds makes the most sense. 30 is more applicable, but this is a matter of opinion. As such, every 30 seconds, it reveals itself + wiggles, but then each time the launcher is revealed, the icon wiggles again. As I said, the highlighted backgrounds just aren't that great to use alone. They either need to be made far more obvious or else incorporate some sort of motion based animation to assist. Non Auto Hide Mode: Option C as listed above. Thanks for your time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319542 Title: Unity urgent animation needs an adjustable time length. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1319542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283775] Re: Launcher: icon pips are not always updated properly
I apologize, I might have been semi incorrect with my post. According to this bug https://bugs.launchpad.net/unity/+bug/1309739 the highlighted offset is a work in progress. It's my understanding that the pips and the highlighted edges are similarly controlled, as in if you fix one you fix the other. That said, it would stand to reason that some of these pips vs highlights bugs would be merged into one, but that doesn't appear to be the case, so maybe they're different. Either way, I cannot put into words enough how soon I want to see that fix land. You'd think it's something that users wouldn't notice, but when it's already a poor way (highlighted edges, that is) to tell that an application needs attention AND they face a bug like this where it has offset highlighting and one pixel sized pips, it makes you realize how much bigger the problem is from a usability standpoint. I mean, just take a look at Skype (really this applies to any application but I'll pick on Skype here). Compare Skype idle vs Skype needing attention. The blue color differences might be two hex shades off, and the thickness is hardly a pixel wider when it needs attention. I mean, THIS is how we tell that we have a notification? This is one area where Windows 7 and OSX got it right. (man it hurts to say that) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283775 Title: Launcher: icon pips are not always updated properly To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283775] Re: Launcher: icon pips are not always updated properly
I hate to sound abrasive as I too, like mentioned above, am an Ubuntu fan, but I'm somewhat surprised to see this hasn't been addressed yet. I'm finding it to be a common question that comes up as users want to know how to tell when an application needs attention. "You mean that faint line color is how I see that I just got a message??" (caused by the mismatched highlight) or "I can't see the dots to see how many firefoxes I have open. How do I adjust it?" I understand this issue was fixed in another report for 7.2.1, but A) where is it? And B) why on earth was this not pushed ASAP? As somebody who lives in the Ubuntu world I can tell you it's not a small frustration by any stretch. Given the fact this makes for a less consistent feeling interface, this turns into a hard sell for users who are used to the nice orange glow of the windows 7 icons needing attention or the continually bouncing icons in osx. That brings up another point as the icon highlights are a far cry from convenient when alerting users they just received a message. On screen popup is great but what about when I wasn't present when I received the message and come back a minute later? It needs to be more obvious without question. The envelope is no where near a logical answer either since few applications support it, plus it makes no sense to look on the upper right side to the envelope just to tell what application from the left side unity bar needs attention. Surely that should raise an eyebrow... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283775 Title: Launcher: icon pips are not always updated properly To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319542] [NEW] Unity urgent animation needs an adjustable time length.
Public bug reported: Ubuntu 14.04, fully up to date, Unity Version: 7.2.0+14.04.20140416-0ubuntu1 The Unity launcher in my setup is not hidden. It is always visible. The current behavior of the urgent animation goes like this: 1) An application needs attention (such as an instant message through Empathy or Skype) 2) Icon wiggles for about one second 3) Once the wiggle is over, the icon remains highlighted The problem is with step 2. The icon never reinitializes any sort of motion to catch the user's eye. People are busy. People are frequently multitasking. In a lot of cases, people are using multiple monitors or very widescreen monitors and their field of vision is in an entirely different place altogether. There really should be some sort of repeated motion that takes place to grab the users attention, thereby signifying that an application needs attention. A few possible solutions would be: A) Let the icon wiggle indefinitely until the user clicks on it. This is a bit obnoxious, because you have to consider the situations where a user might notice it, but might be too deep in a specific project to address it right away. This would stand as a potential distraction and/or annoyance, though it *would* eliminate the chances of the notification going missed. B) To allow the user to adjust the time frame in which the wiggle animation takes place. That way instead of one second, perhaps the user might want it to last 10 seconds, or 30 seconds, etc. There are times where I am engaging in an active conversation but switching to another application frequently. At times, I miss a message altogether despite the fact I'm looking at the screen. This is entirely due to the short time frame in which the urgent animation is moving. The length of time in which it moves is, more times than not, simply not long enough to be noticed. If the one second span could be adjusted, and say I have it set to 5 seconds, or 10 seconds, surely I would notice it. C) The most optimum solution in my opinion is to make the urgent animation continually come up over a specified span of time. Example, I receive a notification from Empathy, but I miss it. It wiggles and shortly thereafter stops wiggling, thereby just sitting idle but with the icon highlighted. A short time later, perhaps 30 seconds later, it wiggles again, and continues onward in 30 second intervals indefinitely until the user gives attention to the application requesting it. Option C would circumvent a potential "annoyance" factor of option A, and it would work around the fact that option B) would require another thing to change in the settings menu. All in all, there *really* should be a way for a user to more easily see that an application needs attention. A simple one second wiggle is not enough. A background highlight is not enough as it does not move to be noticed. You only notice a background highlight if you specifically look at the icon, whereas a motion-based notification (wiggle, etc) actually 'grabs' your attention to be noticed. Thank you for your time, consideration, and hard work. If I can be of any further assistance please let me know. Thank you again! 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: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 14 15:28:24 2014 InstallationDate: Installed on 2014-04-04 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319542 Title: Unity urgent animation needs an adjustable time length. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1319542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776745] Re: Unity's sidebar 'Urgent' icon animation not constant
*** This bug is a duplicate of bug 893196 *** https://bugs.launchpad.net/bugs/893196 Christopher, I appreciate your interest and I thank you for your time. I will submit a new bug report now. Again, thanks. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776745 Title: Unity's sidebar 'Urgent' icon animation not constant To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/776745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776745] Re: Unity's sidebar 'Urgent' icon animation not constant
*** This bug is a duplicate of bug 893196 *** https://bugs.launchpad.net/bugs/893196 @ Christopher Townsend, I see that, but I'm not sure how it's fixed, unless I am totally misunderstanding something. Based on the bug report you linked me, it suggests that this is regarding the Unity bar being hidden. I don't have my Unity bar hidden. My Unity bar is always visible. My issue is this. I just received a Skype message. The icon wiggled. Had I not seen it wiggle, it would have just sat there with a highlight. Ironically enough, the highlight is offset, making it very difficult to see, which is frustrating given it's the only way to tell that Skype needs attention if I miss the wiggle. (highlight issue is currently bug #1309739, but I see you're working on that - thanks!) If I let the Skype notification just sit there, it never wiggles again. What I don't understand is why it doesn't wiggle again. Why doesn't it re-notify me? This wiggling one time only thing doesn't really align with design logic. People are busy. People multitask. People will miss that one second it happens to wiggle quite frequently. Some sort of reoccuring notification until the user gives that application attention is basically what I am referencing. Am I missing something, or is this option here and I just not know about it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776745 Title: Unity's sidebar 'Urgent' icon animation not constant To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/776745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776745] Re: Unity's sidebar 'Urgent' icon animation not constant
*** This bug is a duplicate of bug 893196 *** https://bugs.launchpad.net/bugs/893196 So here we are in 2014... no change... Come on... How does something like this need any sort of monumental review? It's a frustration that a huge amount of users have. It's wildly easy to miss notifications because of the way it's currently implemented in Unity. Just give us the option (or better yet, a default, but we know how defaults go around here...) to allow the icon to continually wiggle every so often until the user clicks on that icon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776745 Title: Unity's sidebar 'Urgent' icon animation not constant To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/776745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] Re: libsdl1.2 always uses backingstore which causes tearing in modern X servers
Sorry Timo, just had to share the good news with my own little +1. :) Thanks for the information regarding the process too as I was not aware of that. I'm sure I speak for everone when I say we thank you for the PPA to circumvent this issue until it arrives in the main repo. Your time is appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/libsdl/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280665] Re: libsdl1.2 always uses backingstore which causes tearing in modern X servers
I was having screen tearing on Ubuntu 14.04 with XBMC 12.3 & 13.0. Never had tearing on VLC or smplayer though but no matter what I did it continued on XBMC. Once I added the ppa, exited XBMC and reopened it, tearing is gone. Thank you for the immediate fix! Devs - *please* merge this into 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280665 Title: libsdl1.2 always uses backingstore which causes tearing in modern X servers To manage notifications about this bug go to: https://bugs.launchpad.net/libsdl/+bug/1280665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309751] Re: Unity does not properly search everything depending on pattern of previous search.
Here's a video depicting it: https://www.dropbox.com/s/2jxvef0hd1dkqwz/unity-dash-search-bug.mp4 So to recap, here's what happens. If you search for something, whether or not you open it, the next search is not a "full" search. What happens: 1) Open dash via super key 2) Type libreoffice 3) Close dash via super key 4) Open dash via super key 5) Type yourfile.odt What should happen is Unity should find yourfile.odt, but Unity does *not* find it. If you hit esc prior to step 5, Unity WILL find it. It's as if hitting the esc key (and thereby deleting everything in the dash search) reinitializes a FULL scan. Is there a way to turn off the dash history? If Unity isn't even trying to save prior searches (which is useless anyway), then this would circumvent the problem altogether as it would force Unity to do a full scan each time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309751 Title: Unity does not properly search everything depending on pattern of previous search. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1309751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302663] Re: Unity's "Scale UI" function problematic on some devices.
It seems as if the final release of 14.04 has fixed this. Either that, or I just magically got lucky on the 4-5 different model systems I'm using 14.04 with. Before, it seemed like it had a hard coded 1-4 option available in the scaling. If you hit a certain point when scaling up, you would hit the point of no return, where you could not scale down Unity properly (via GUI) and if you tried to ALT + click/hold and drag, Unity would crash. So far I have yet to see that again. Likewise, it seems as if the system is more intelligent when it comes to the scale. I used to be able to scale this 1366x768 laptop to 4, but now I can only go to 1.38. I have to wonder if the system now detects user environment settings and only offers available options below the problematic threshold. At any rate, I'm not seeing this issue anymore. Is anybody else? Thanks for your assistance everybody (anybody reading this, all of our wonderful developers, etc), and thank you Marco for that FYI. Have a good one! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302663 Title: Unity's "Scale UI" function problematic on some devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310871] [NEW] Music lens does not play music through default music player.
Public bug reported: Ubuntu 14.04 64 bit. Fresh install, all updates applied. If I browse for music in the music lens and play them, they open in Rhythmbox. System Settings >> Details >> Default Applications has the default music player set to Clementine. I should also note that the Rhythmbox dash plugin is DISABLED, while the Clementine dash plugin is ENABLED, and even still it pipes the music through Rhythmbox. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 21:46:45 2014 InstallationDate: Installed on 2014-04-04 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-lens-music (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310871 Title: Music lens does not play music through default music player. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1310871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968974] Re: Some free applications looks like paid applications with price 0.00 and with buy button
This seems to -still- be an issue on 14.04 with applications such as Nitro Tasks and Steam... There hasn't been any discussion in quite some time so I figured I'd make note about 14.04 in particular. It sure is a confusing task when a new Ubuntu convert fires it up and realizes they have to set up an account to log in to the service before "purchasing" the free application they're intending to install... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968974 Title: Some free applications looks like paid applications with price 0.00 and with buy button To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/968974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309751] [NEW] Unity does not properly search everything depending on pattern of previous search.
Public bug reported: I have noticed in Unity that sometimes it does not properly search everything. By everything I mean items outside the scope of applications, but also documents, folders, etc. I found this very easy to replicate. 1) Create a LibreOffice document entitled Passwords (aka Passwords.odt) 2) Search for LibreOffice in the dash. Without opening anything, hit the super key to exit the Unity dash. 3) Hit the super key and type "passwords". Note that only "Passwords and Keys" (application) shows up, when you should see Passwords.odt and "Passwords and Keys". Now if you repeat steps 2 and 3 again, but this time hit backspace to erase LibreOffice, then type Passwords, you'll see Unity kind of does a fully reset search, thereby digging up other items outside of applications that resemble the search term "Passwords". Given that Unity is meant to be the centralized finder of all things, it would make sense if Unity would search for all *local* items with all searches without the need to backspace. Before I figured out that hitting backspace kind of reset the Unity search to find more things outside the applications realm it was wildly confusing with how Unity would seemingly often find the document I wanted but other times only found applications that I didn't want. Thanks for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 18 16:42:26 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.80 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 18 15:14:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309751 Title: Unity does not properly search everything depending on pattern of previous search. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1309751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012204] Re: Is not clear enough when an application has information or not
Unfortunately, I share the exact same view as you do. Unfortunately x2, it's even more of a headache in 14.04. It seems as if the icons were switched to SVG to allow for better scaling on HiDPI screens, but at the expense of the pips being much smaller than before and the highlights of the icons being almost identical from their idle state. I reported my own bug report and haven't had that much activity on it, granted it's still a young report, although it's been listed as 'low importance', which of course given the fact there's little/no way to decipher an icon's status, this has me a little concerned to say the very least. Still crossing my fingers there... Here are some examples in 14.04 with Skype in particular: http://oi62.tinypic.com/nxjgh3.jpg http://oi59.tinypic.com/21mi1w0.jpg >From bug report: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073 See how there's literally no difference? It's such a minor difference it's difficult to see even when you're actively watching the icon switch back and forth, let alone having to look at an icon when you get back to your computer to quickly see "does this application need attention?" As it stands now, it's clearly a broken feature as it's pretty much impossible to tell the difference. Hopeful that there's a quick resolution. I'd certainly hate to see the next LTS be stuck with something like this throughout its cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012204 Title: Is not clear enough when an application has information or not To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1012204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304073] Re: 14.04 Unity pips (white dots in bar) are now too small.
As I re-read my bug report I decided that I needed to have an easier way for developers to quickly see what I'm referencing. I made some animated gif's which makes this far easier to quickly tell the difference. There are two animated gif's. One is with the "backgrounds on open applications only" as well as "colored edges." That way you can see how different options look similar or different. In both scenarios I was using Skype as an example. One slide shows Skype with no unread messages, the next shows Skype with an unread message (aka, needing attention). You can clearly see how crazy similar each gif is with both no unread messages vs unread messages available (aka application needs attention). This is extremely difficult for users to quickly decipher, did I get a message? Do I need to check that application? It was far, far easier in 13.10 and below to quickly tell the difference. Examples: http://oi62.tinypic.com/nxjgh3.jpg http://oi59.tinypic.com/21mi1w0.jpg Of course, this would be less of an issue if all applications that are built on any sort of messaging platform (whether it be email, instant messaging applications, webapps such as gmail, twitter, etc) would properly utilize the numbering system for alerts. What I'm referencing is when you get a new message on, say, Empathy, and a "1" shows up overtop of the Empathy icon on the Unity bar. Unfortunately this seems to be broken in 14.04, as I reported here (take note of the Pidgin icon with the "2" on the icon within the included screenshot of this report): https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304186 But as it stands now, that integration isn't working and the highlighting differences are too similar to tell if an application has a highlight without having the Unity icons absolutely huge. Again, thank you very much for your time and dedication. I just wanted to make sure that my report was as accurate and easy to understand as possible. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304073 Title: 14.04 Unity pips (white dots in bar) are now too small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304073] Re: 14.04 Unity pips (white dots in bar) are now too small.
I believe it's also worth noting that the way the icons get highlighted when they need attention has changed as well. In 13.10 and prior, all four sides of the icon highlighted. In 14.04, it's just two of the four sides (left + top sides). In some cases it seems that only the top edge of the icon when highlighted shows any difference, and even then it looks nearly identical when I click on the icon, thereby removing the highlight. Meanwhile, the left side of the icon that also gets highlighted seems to not change. I understand that these items were changed as part of the conversion process to SVG, allowing them to scale up and look great on HiDPI screens. While I support this very much, it really does feel like a usability regression as it is now more difficult to tell when an application needs attention. If *everything* supported the Message Tray, this would be less of an issue as a user could just look there and see what took place. To be quite frank, the Message Tray certainly isn't supported by all applications, so you might see my angle on this now. Take into consideration that somebody may get up from their computer for a moment and come back several moments later. If the icons do not clearly depict that they received a message, or somebody highlighted them on IRC, etc., they wouldn't otherwise know. Given the fact that the current highlight is less obvious and the pips are smaller (making it more difficult to tell if a pip is blue or white to signify the difference), suddenly it becomes a burden to the user. Thinking it was the fact that I had selected "colored edges" for the "icon backgrounds" feature, I set everything back to default, just as it comes out of the box in 14.04, so then the icons had a solid color background without any colored edges. Sadly, this was no change (if anything, it was slightly worse since I didn't even have two of the four highlighted edges). In that case, I had to rely entirely on the color of the now smaller pips, which is cumbersome and quite a hassle. I still believe that having the ability to scale the pips independently would be a wildly effective method so the user may choose based on their preference, but with how close we are to release, at the very least I would favor seeing a more 13.10-ish size of pips on my 14.04 installs. Based on my conversations with users, it sounds like a lot of people don't notice this change. That said, I certainly notice when my messages go missed until I happen to message them again when they are in front of their system, thanks to the notification in the upper right corner on their display. :) Again, thank you for your time and efforts. Have a great day! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304073 Title: 14.04 Unity pips (white dots in bar) are now too small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302663] Re: Unity's "Scale UI" function problematic on some devices.
Hello. I am on my same laptop as I was above when I posted this bug report and after fully updating I noticed some differences. It seems as if the scaling feature must be taking my resolution into account so it doesn't scale the UI so far that I cannot revert back. Before, I could scale from 1 (default) to 4. Now I can only scale from 1 to 1.38. If the assumption I just mentioned (scaling takes resolution into account to prevent over-scaling to the point of no return), then this is a welcome addition. Nonetheless, I wanted to ask/mention it here for some more insight as I'm curious if my assumption is correct. Thank you for your time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302663 Title: Unity's "Scale UI" function problematic on some devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302803] Re: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not restart.
The only kernels I was able to test were 22-generic and 23-generic of 3.13. Both yielded the exact same results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302803 Title: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188774] Re: 8086:0126 [Lenovo ThinkPad Edge E430] [snb] 13.04 goes into hard lock mode randomly.
Sridhar, are you still having consistent issues as you had on 13.04? On my laptop in particular, I have had no issues since the spawn of 13.10. I've been running 14.04 beta for a few days and that too has been problem free in terms of freezing. I can't help but to wonder if the 3.8-3.9 series kernel was the problem. I read similar reports with other distros using these kernels as well. If I recall, I believe I even ran Fedora and had it hardlock using the 3.9 kernel (3.9.3 or something?). At any rate, 3.10 and above seems to have helped. Just wanted to throw in an update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188774 Title: 8086:0126 [Lenovo ThinkPad Edge E430] [snb] 13.04 goes into hard lock mode randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1188774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304186] [NEW] 14.04 Unity integration with messaging applications not fully working.
Public bug reported: On the three 14.04 installs I've done, I've noticed this same situation come up. As seen in the screenshot below, when you receive an instant message you get a number on top of the messaging application in the Unity bar. This isn't the case in 14.04. http://www.omgubuntu.co.uk/wp- content/uploads/2011/04/screenshotae_thumb.png With both Pidgin and Empathy (using Google Talk), I do not receive the number on the icon to indicate how many new messages I have. With Empathy in particular I did notice that brand new conversations do list a "1" there, but once I engage in conversation and later background Empathy, new messages do not put a number on the icon to indicate that I have unread messages. In prior releases of Ubuntu, this seemed to always work. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 8 01:40:10 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5000] InstallationDate: Installed on 2014-04-04 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) MachineType: LENOVO 3254CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=58de4412-6390-4ffc-abeb-3d7978795c18 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET32WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO 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:bvrH0ET32WW(1.14):bd06/15/2012:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140404-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 20:54:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5225 vendor CMN xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304186 Title: 14.04 Unity integration with messaging applications not fully working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304073] [NEW] 14.04 Unity pips (white dots in bar) are now too small.
Public bug reported: On all 14.04 installs I've tinkered with so far they've all exhibited this behavior. The pips (white dots) next to the icons in the Unity bar are too small. I never noticed this before, so I went back to a 13.10 install to compare. The pips on 14.04 are so small that they, quite frankly, feel useless. They need to be of adequate size in an effort to be easily seen by the user, regardless of the actual icon size. Take note of the size of the white pips on the Unity launcher in the following screenshots. https://www.dropbox.com/sh/mc4k4yyjm5nbbzk/4t6SgqVN8H Here's an alternative 'direct download' link to the images just in case: http://skynetcore.org/shared/pips.tar.gz In an effort to present an accurate comparison I included the following screenshots (note that 48 px on both 13.10 and 14.04 seem identical, it's just the smaller sizes that down-scale too far) 13.10 - 32 px 14.04 - 32 px 13.10 - 48 px 14.04 - 48 px I also included a 5th screenshot of 26 px in 14.04 in case it helps further show what I'm referencing. While scaling the size of the pips makes sense to a certain degree, the current behavior scales them far too small. I feel as though they should have (at minimal) a 13.10 oriented type of scaling so they are more easily viewable, and therefore, more useful. If they could be adjusted in size, that would be a monumental bonus as well, but I have a feeling that might be a stretch for the given time frame. :) Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 7 17:41:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 17:24:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304073 Title: 14.04 Unity pips (white dots in bar) are now too small. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
This is still an issue on all of my 14.04 installs right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299872] Re: Quassel Client won't start with recent updates (3/30/2014)
With my issue in particular, I just reinstalled 14.04 since the laptop I was running 14.04 on at the time was a spare unit. Once I reinstalled, it was fine. Prior to reinstalling, I wiped everything in my home directory including the hidden items; no change. Sorry it doesn't really help, but given the fact another user reported similar weirdness, it at least confirms that I'm not crazy. :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299872 Title: Quassel Client won't start with recent updates (3/30/2014) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1299872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302804] [NEW] amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not resume from suspend properly (nothing clickable).
Public bug reported: Hello friends. I have a late 2009/early 2010 clamshell Macbook. When I close the lid OR select suspend from the menu, it appears to successfully suspend. The light on the front of the laptop has a steady bright/dim pulse, so things look good there. When I resume from suspend, everything comes awake again. Thing is, nothing is clickable. I can see the lock screen, but I cannot click on anything. The cursor freely moves, however, but nothing responds to my click request. I also disabled the "lock system when resuming from suspend" option in hopes that maybe it was a lock/login screen issue. In this case, it brings me back to my regular desktop. I see the Unity panel, top bar, etc. But once again, anything I click on is unresponsive. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-22-generic 3.13.0-22.44 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 1888 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 4 15:53:02 2014 HibernationDevice: RESUME=UUID=916319a9-c577-4321-a5a9-666cb1904590 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64+mac (20140404) MachineType: Apple Inc. MacBook6,1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=ff973b06-cfee-499c-803a-e740e2e2b040 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00C8.B02.1003151501 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00C8.B02.1003151501:bd03/15/10:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302804 Title: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not resume from suspend properly (nothing clickable). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302804] Re: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not resume from suspend properly (nothing clickable).
I should also note that I am using the amd64+mac ISO daily build fully updated as of today, April 4th 2014. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302804 Title: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not resume from suspend properly (nothing clickable). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302803] [NEW] amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not restart.
Public bug reported: Hello friends. I'm running a 2009/2010 clamshell Macbook with today's (April 4th 2014) daily build fully updated. I noticed I can not restart the computer. When I shut down, it works fine. It also goes through its full startup just fine. When I select restart from the menu, I see the splash screen (which is very jagged and unreadable). I see the scattered dots highlight red to indicate progress once or twice, then they lock up. The system never actually restarts and I must hold down the power button to force it off before I can restart again. This is also true when I issue 'sudo reboot' from the terminal. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-22-generic 3.13.0-22.44 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 1888 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 4 15:48:06 2014 HibernationDevice: RESUME=UUID=916319a9-c577-4321-a5a9-666cb1904590 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64+mac (20140404) MachineType: Apple Inc. MacBook6,1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=ff973b06-cfee-499c-803a-e740e2e2b040 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-22-generic N/A linux-backports-modules-3.13.0-22-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00C8.B02.1003151501 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00C8.B02.1003151501:bd03/15/10:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302803 Title: amd64+mac ISO daily build + 2009/2010 clamshell Macbook does not restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302777] [NEW] Bluetooth turns itself off continuously.
Public bug reported: Ubuntu 14.04 64 bit daily build, fully updated to today (April 4, 2014). I noticed on my Lenovo E430 when I try to enable bluetooth, it continuously disables itself. I installed "Bluetooth Manager" from the Software Center and it activated and stayed lit like it should have. Once I removed Bluetooth Manager, disabled Bluetooth, and tried to enable again, it failed despite having the default "Bluetooth" application installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 15:06:15 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 3254CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=58de4412-6390-4ffc-abeb-3d7978795c18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET32WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO 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:bvrH0ET32WW(1.14):bd06/15/2012:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302777 Title: Bluetooth turns itself off continuously. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1302777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302663] [NEW] Unity's "Scale UI" function problematic on some devices.
Public bug reported: I'm running a fully updated (as of 4/1/2014) install of Ubuntu 14.04 64 bit. This is on a Toshiba ultrabook with a mobile i5 processor and a 13.3" screen @ 1366x768. Earlier I was messing with the scale UI mode of the system settings >> display field. I set my UI scale to be maxed out at 4. Once done, windows were so large it was impossible to see. I couldn't even see any options within system settings besides two. Scrolling of course helped a bit but it was largely cumbersome. Once I went into the displays section to turn UI scaling back down to 1, I realized the function was far out of reach on my screen. I tried to hold down ALT and click to drag the window up beyond the top edge, but Unity crashed. In fact, every single time I hit the ALT key and clicked to drag, Unity crashed. Once Unity crashes 2 or 3 times, it doesn't come back without a hard power down and full startup. On the flip side, I plugged in an external monitor with a resolution of 1440x900. Once done, suddenly ALT worked and I had no crashes. I was able to drag the displays window up until I could see the UI scaling feature and turn it back down to 1. There's a few issues here that I feel need to be addressed, since there's little doubt that people will tinker with these functions. After all, these features are baked directly in to the interface as available parameters, but as notated above, settings (such as 4) render the system into a non-usable (and non-fixable without accessive tinkering) state. Is there a way higher UI scaling modes can be altered for easier scrolling or maneuvering of windows to reset it back if need be? Perhaps a work around could even be a "reset to defaults" button at the top bar? After all, with a UI scaling of 4, I could see the top of the window - just very little else. If I could have reset to default that would have alleviated any headaches. Thanks for all of your hard work! It's appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 4 11:10:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 4 11:08:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6637 vendor ACI xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302663 Title: Unity's "Scale UI" function
[Bug 1299872] [NEW] Quassel Client won't start with recent updates (3/30/2014)
Public bug reported: I'm running Quassel Client on an Ubuntu 14.04 laptop, along with Quassel Core on my Ubuntu 12.04.4 server. My client machine is running Quassel Client from the standard trusty repos. This morning I checked for updates and acquired quite a number of them. Following a restart, Quassel Client will not start. I can see the processes populating in System Monitor and I can kill them accordingly, but Quassel Client itself just never actually runs, even following a reboot. I also removed my ~/.config/quassel-irc.org folder in an effort to reset the settings, but no change. Thank you for your time and efforts! I'm running Quassel Client on an Ubuntu 14.04 laptop, along with Quassel Core on my Ubuntu 12.04.4 server. My client machine is running Quassel Client from the standard trusty repos. This morning I checked for updates and acquired quite a number of them. Following a restart, Quassel Client will not start. I can see the processes populating in System Monitor and I can kill them accordingly, but Quassel Client itself just never actually runs, even following a reboot. I also removed my ~/.config/quassel-irc.org folder in an effort to reset the settings, but no change. Thank you for your time and efforts! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: quassel-client (not installed) ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 30 14:53:07 2014 InstallationDate: Installed on 2014-03-19 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) SourcePackage: quassel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: quassel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299872 Title: Quassel Client won't start with recent updates (3/30/2014) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1299872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299872] Re: Quassel Client won't start with recent updates (3/30/2014)
Once I submitted the bug I noticed this line in the automatically generated output above. Package: quassel-client (not installed) I do apologize, I actually installed quassel-client-qt4 but accidentally ran the ubuntu-bug apport against quassel-client. If any additional information is needed that might be missing due to my goof up please let me know and I'd be happy to provide that information. Thanks again! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to quassel in Ubuntu. https://bugs.launchpad.net/bugs/1299872 Title: Quassel Client won't start with recent updates (3/30/2014) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1299872/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1255558] Re: Can't type my password after cold boot
Forgot to mention that clicking other items at the login screen often times allows me to type in my password. Also, typo correction from above comment - meant to say "just NOW I had to reboot..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255558] Re: Can't type my password after cold boot
I'm running Friday's daily build (3/14/2014), fully up to date as apt- get update && apt-get dist-upgrade yields nothing available, and I am still having this issue. In fact out of 12 to 15 boots I only saw it twice, but just not I had to reboot about 14 times to get a boot that allowed me to log in. Is there something in the 3/15 daily that the 3/14 excludes, even from a dist-upgrade level that might yield a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287987] [NEW] Selecting "quit" from Unity bar does not close Rhythmbox.
Public bug reported: The quit functions of Rhythmbox do not act consistently, which doesn't make a lot of sense. With Rhythmbox open, CTRL + Q along with Rhythmbox (in global menu) >> Quit will actually, 100% quit the application to the point that currently playing music gets stopped immediately. On the flip side, if you right click Rhythmbox in the Unity bar and select quit, it simply closes the window, but Rhythmbox continues to function in the background and play music. It would make more sense if the quit functions would actually quit the application, as the "quit" function in the Unity bar feels a bit confusing after it doesn't truly quit Rhythmbox. Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Mar 4 19:06:21 2014 InstallationDate: Installed on 2014-01-14 (49 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287987 Title: Selecting "quit" from Unity bar does not close Rhythmbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1287987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275856] Re: Nautilus crashes when renaming items on Samba share.
I tried to open it with the submit report utility, but it does nothing. It asks me if I want to report it, I hit continue, and nothing else happens after that. Same thing happened when I launched it via terminal as you suggested. Apport is enabled. Instead I'm attaching it here. Hope that's okay. ** Attachment added: "_usr_bin_nautilus.1000.crash" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+attachment/3967939/+files/_usr_bin_nautilus.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275856 Title: Nautilus crashes when renaming items on Samba share. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275856] [NEW] Nautilus crashes when renaming items on Samba share.
Public bug reported: Ubuntu 13.10 64 bit Fully updated When I connect to my samba server (Ubuntu Server 12.04.4 64 bit), I am able to create and move files around. I tried to rename a directory and it crashed. It crashes, seemingly, 100% of the time when I try to rename the directory. In paritcular, the relevant line of syslog is: Feb 3 12:37:53 JS-Z835 kernel: [ 203.805694] nautilus[3952]: segfault at 20 ip 00430e7f sp 7fff70930fb0 error 4 in nautilus[40+153000] The above results are on a Toshiba ultrabook. I duplicated this on a separate laptop by Lenovo, but also with Ubuntu 13.10 64 bit and fully updated. The only relevant line I saw of the syslog on that system is: Feb 3 12:45:00 JS-E430 kernel: [ 40.812722] nautilus[1981]: segfault at 30 ip 00430e7f sp 7fff91bbf280 error 4 in nautilus[40+153000] What is admittedly a little strange is when I was about to submit this report, I hopped back on the network share and for a handful of times I was able to rename a few directories without issue. I exited Nautilus, re-opened it, and now it's crashing again. Just wanted to notate that as it seemed as if it wasn't immediately replicable. If there is any sort of testing I can do please let me know. Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 3 12:39:10 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'840x550+49+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2014-01-28 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275856 Title: Nautilus crashes when renaming items on Samba share. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054776] Re: Don't include remote searches in the home lens
So let me get this straight... 100% of the time when I type into the dash, my system is searching for online resources relevant to what I typed. That said, 99% of the time I type into the dash, I am doing so to retrieve a local file or application. So roughly translated, 99% of the time Unity is bringing me irrelevant search results that ultimately slow down my computer in an obviously noticeable fashion when typing in search terms. Who on earth thought this was a good decision? I can see the value in an online resource like this, but being opt-out is ridiculous. It being in the home lens is even more ridiculous. Why would you split up lenses for music, videos, files, applications, but NOT online resources? I just can't fathom this. Given the fact I often have to order parts for different things at work through Amazon, I would love to support Canonical by going through the lens facet, but not at the expense of my privacy. I repeat, not at the expense of my privacy. Canonical, you have done so much good for the Linux community. You deserve to be commended 100x over again for your work. You've taken some insane chances along the way. Unity has evolved into a beautiful, clean, and professional desktop environment. It was met with criticism but it has blossomed into something that's really quite nice. Mir has yet to be seen so I can't really comment there quite yet. Then you have this shopping lens being an opt-out feature. I honestly don't understand how someone sat at the meeting table and thought "this is a good idea." This is distribution suicide. You're losing a magnitude of users over this stupid nonsense little thing. Is this really worth all of the negative publicity Ubuntu/Canonical is *still* receiving (and forever will) over this? I mean, really? Is it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054776 Title: Don't include remote searches in the home lens To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-shopping/+bug/1054776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262736] Re: Add Pantheon to "OnlyShowIn" entry to /usr/share/applications/vino-preferences.desktop
Hi there. Thank you for your response. I'll surely list this upstream, as I do indeed consider this to be a really, really annoying bug that is easily fixable. Realistically speaking, having a line like OnlyShowIn does nothing except inhibit users from utilizing this software on other desktop environments. "Official" or not, a desktop environment is a desktop environment and shouldn't be ignored with a silly line like that. Again, thanks for your time. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262736 Title: Add Pantheon to "OnlyShowIn" entry to /usr/share/applications/vino- preferences.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1262736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262736] [NEW] Add Pantheon to "OnlyShowIn" entry to /usr/share/applications/vino-preferences.desktop
Public bug reported: Hi there. I use elementary OS, which is based on Ubuntu 12.04. Elementary OS uses the Pantheon desktop environment, which is based entirely on GTK 3. I installed vino so I could enable remote VNC access, but it did not show up in my applications menu. After some digging I found that the /usr/share/applications/vino-preferences.desktop file contained an OnlyShowIn entry with only Gnome and Unity listed. If Pantheon could be added to the list, this would remove a lot of headache for a lot of users who could benefit from this software. Thank you for your consideration! ** Affects: vino (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262736 Title: Add Pantheon to "OnlyShowIn" entry to /usr/share/applications/vino- preferences.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1262736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262735] [NEW] Add Pantheon to "OnlyShowIn" entry in desktop file.
Public bug reported: Pantheon is a desktop environment based on GTK 3 in use by the elementary OS team. Elementary OS, for what it's worth, is based on Ubuntu 12.04. Pantheon is becoming more popular and packages for it already exist in Arch and openSUSE. Unfortunately, Pantheon's file manager has had some stability issues, so I've installed Nautilus. Like many others, we were confused as to why Nautilus was not showing up in the applications menu. After some digging I found the OnlyShowIn entry in /usr/share/applications/nautilus.desktop and, quite honestly, just commented out the whole thing. Suddenly, Nautilus worked - success! That said, countless others have looked to install an alternative file manager, such as Nautilus, only to find it doesn't show up. They assume it's not supported and move on to other alternatives. If Pantheon could be added so elementary OS could pick up Nautilus that would be tremendously useful to a lot of users. Thank you for your consideration! ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262735 Title: Add Pantheon to "OnlyShowIn" entry in desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1262735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233759] [NEW] Ubuntu GNOME 13.10, Evolution 3.8.4, crashes when in preferences to EWS account.
Public bug reported: Ubuntu GNOME 13.10 Evolution 3.8.4 No PPAs Fully updated (Tues Oct 1, 2013) I have 3 accounts associated with Gnome Online Accounts. Two Google, and One Exchange (EWS). Often times when I go into Edit - Preferences, click on my Exchange EWS account and hit edit, Evolution crashes. I have yet to see it crash when I replicate these steps to the Google email accounts, but it happens on the EWS account rather frequently. It took me 5 times to go in and change the receiving time option from 60 minutes to 1 minute, as an example. Oddly enough, just seconds ago I was preparing to close this bug report because Evolution wasn't crashing despite me clicking around in the preferences window. I left it sit untouched for about 15 seconds and it just disappeared cold turkey out of no where. Thanks for your time! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 1 12:41:59 2013 InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 (20130930) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233759 Title: Ubuntu GNOME 13.10, Evolution 3.8.4, crashes when in preferences to EWS account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1233759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176379] Re: Streaming videos over LAN with GVFS often locks up VLC Media Player in Ubuntu 13.04
Just fired up Ubuntu GNOME 13.10 preview. VLC is doing the same thing here yet again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176379 Title: Streaming videos over LAN with GVFS often locks up VLC Media Player in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205579] [NEW] 1.1.0 does not pick up newly installed applications.
Public bug reported: I recall this issue being fixed, but I spent some time away from Kubuntu and just came back and noticed it again. If I run killall homerunviewer, newly installed applications show up, but othewise I won't see them unless I do a reboot, which would obviously kill and restart homerunviewer in the same way as I mentioned above. Kubuntu 13.04 64 bit Homerun PPA enabled ** Affects: homerun (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205579 Title: 1.1.0 does not pick up newly installed applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/homerun/+bug/1205579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1180156] Re: Brightness keys not working Lenovo E430.
I got it working with the windows 2012 grub boot parameter that I found on Google, which reads: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=\"!Windows 2012\"" I also noticed starting with Linux kernel 3.10, this is supported out of the box with no need to put in any grub parameters. Thank you. -J On Jul 23, 2013 9:10 AM, "Sundaravenkataraman" <1180...@bugs.launchpad.net> wrote: > Hoping that this link will be useful to all... > > http://askubuntu.com/questions/293925/brightness-buttons-not-working- > properly > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1180156 > > Title: > Brightness keys not working Lenovo E430. > > Status in “linux” package in Ubuntu: > Expired > > Bug description: > Ubuntu 13.04, Lenovo E430. > > The brightness keys on this laptop act a little strange. If I hit the > brightness down key, it will drop the brightness to about 1%. If I > press brightness up, it does nothing at all. I see the pop ups come up > as if it's trying, but it never actually changes the brightness at > all. > > If I go into the brightness and lock menu from system settings and > adjust the brightness via the slider it works absolutely fine. This > makes me wonder a few things. What is the difference between the > function keys and the slider in system settings? How is it one works > and the other doesn't? Is there a way to re-map the function keys to > adjust the brightness slider? > > Also - I tried the mainline 3.9 kernel and it acted 100% identical to > the Ubuntu 3.8 kernel. > > ProblemType: Bug > DistroRelease: Ubuntu 13.04 > Package: linux-image-3.8.0-19-generic 3.8.0-19.30 > ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 > Uname: Linux 3.8.0-19-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.9.2-0ubuntu8 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: jason 2027 F pulseaudio > CurrentDmesg: [ 12.393178] input: TPPS/2 IBM TrackPoint as > /devices/platform/i8042/serio1/serio2/input/input13 > Date: Tue May 14 21:06:12 2013 > HibernationDevice: RESUME=UUID=504647a2-9377-4a75-9669-218848b4ee6b > InstallationDate: Installed on 2013-05-14 (0 days ago) > InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 > (20130424) > MachineType: LENOVO 3254CTO > MarkForUpload: True > ProcEnviron: >TERM=xterm >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic > root=UUID=fa9f5123-ae3f-48f6-9132-94a21bf14459 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-3.8.0-19-generic N/A >linux-backports-modules-3.8.0-19-generic N/A >linux-firmware1.106 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/27/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version: H0ET91WW (2.51 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 3254CTO > 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:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.name: 3254CTO > dmi.product.version: ThinkPad Edge E430 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180156/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180156 Title: Brightness keys not working Lenovo E430. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203341] [NEW] 13.10 - Gnome 3.8.3 - Power button shutdown action shuts down regardless of setting.
Public bug reported: Ubuntu GNOME 13.10 64 bit alpha Gnome 3.8.3 Regardless of what the power button action setting is set to, it shuts down my laptop each time. I tried suspend, interactive, etc., it simply shuts down the laptop regardless of the setting. Perhaps this functionality in Gnome Tweak Tool is not mapped to the dconf entries properly? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 20 13:25:55 2013 InstallationDate: Installed on 2013-07-08 (12 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130707) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203341 Title: 13.10 - Gnome 3.8.3 - Power button shutdown action shuts down regardless of setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1203341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424956] Re: nautilus crashed with SIGABRT in raise()
Apport brought me here. Using Ubuntu GNOME 13.10 alpha and it came up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/424956 Title: nautilus crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/424956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
I'm not sure if the issue I am facing is exactly the same or not, but I figured I'd chime in. In my case, copying a single large file works, but copying a dozen files 1-2MB in size (each) locks up when using Nautilus and GVFS. Oddly enough, I only have this issue on my Lenovo, not my Toshiba. The Lenovo is an AMD APU E450 unit, so it doesn't exactly have a ton of horsepower. It does however have 6GB of RAM and an SSD. My Toshiba on the other hand has a mobile i5, 6GB RAM, and SSD. So all things compared, they stack up against each other decently with the exception of the CPU. I have yet to have a successful transfer with multiple small files on the Lenovo. Meanwhile, the Toshiba works brilliantly each and every time. Both are running Ubuntu GNOME 13.04 64 bit, fully updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195093] [NEW] Ubuntu GNOME 13.10 - No battery indicator.
Public bug reported: As the title says, I have no battery indicator in my panel of Gnome Shell in Ubuntu GNOME 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-shell 3.8.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 26 23:03:55 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130625) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195093 Title: Ubuntu GNOME 13.10 - No battery indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1195093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195083] [NEW] Windows 2012 Grub parameter passes as Windowsx202012
Public bug reported: I was testing Fedora 19 when I realized my brightness controls did not work predictably. If I hit brightness down, it did nothing. If I hit brightness up, my brightness went to about 1% and stayed there indefinitely. Thinking this was similar to what I had to do in Ubuntu GNOME 13.04 (add the Windows 2012 Grub parameter), I did so, and it fixed it. On Fedora 19, it did not fix it. So why might you be asking am I talking about Fedora in an Ubuntu bug report? I just fired up Ubuntu GNOME 13.10 and tried the same thing, and it acts 100% identical. jason@JS-E430:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic root=UUID=984ddcf5-7b38-410b-9398-6edb27732c20 ro quiet splash "acpi_osi=!Windows\x202012" Now I'm wondering if this is a kernel issue. Both distros are on 3.9.X. The only work around I have now is to add the brightness extension for Gnome and use that to control my brightness. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-7-generic 3.9.0-7.15 [modified: boot/vmlinuz-3.9.0-7-generic] ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 1683 F pulseaudio Date: Wed Jun 26 22:39:40 2013 HibernationDevice: RESUME=UUID=504647a2-9377-4a75-9669-218848b4ee6b InstallationDate: Installed on 2013-06-26 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130625) MachineType: LENOVO 3254CTO MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-7-generic root=UUID=984ddcf5-7b38-410b-9398-6edb27732c20 ro quiet splash "acpi_osi=!Windows\x202012" RelatedPackageVersions: linux-restricted-modules-3.9.0-7-generic N/A linux-backports-modules-3.9.0-7-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO 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:bvrH0ET91WW(2.51):bd02/27/2013:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195083 Title: Windows 2012 Grub parameter passes as Windowsx202012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188774] Re: [snb] 13.04 goes into hard lock mode randomly.
Sorry to spam the bug report, but the solution listed in the above bug report did nothing. I just had my 4th lockup today. Any ideas to get STA working on 3.9/3.10 to do further testing? Otherwise this will be a dead end for the time being as I cannot swap wireless cards in this laptop thanks to Lenovo locking things down in an obnoxious manner. Any other insight would be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188774 Title: [snb] 13.04 goes into hard lock mode randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1188774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs