[Bug 696038] Re: system user appears in login list of users
[2011-03-15 11:41:46] soren@lenny:~$ sudo ck-history --frequent [sudo] password for soren: ** (ck-history:22914): WARNING **: Unable to parse session removed event: seat-id='Seat1' session-id='Session171' session-type='' session-x11-display='' session-x11-display-device='' session-display- device='/dev/???' session-remote-host-nam1297175131.310 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0 ** (ck-history:22914): WARNING **: Unable to parse session removed event: seat-id='Seat1' session-id='Session2405' session-type='LoginWindow' session-x11-display=':0' sess1292664169.926 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0 nova 56767 soren7945 root 495 gdm 126 rabbitmq 116 [2011-03-15 11:41:59] soren@lenny:~$ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/696038 Title: system user appears in login list of users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 696038] Re: system user appears in login list of users
I only see nova on the list, though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/696038 Title: system user appears in login list of users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 708911] Re: GDM considers only users with uid 500 system users
** Branch unlinked: lp:~ubuntu-desktop/gdm/ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/708911 Title: GDM considers only users with uid 500 system users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 708911] [NEW] System users are shown in login screen if they've recently logged in
Public bug reported: Binary package hint: gdm Due to the way they start, certain system users turn up in ck-history's output. Debian Policy defines a system user as someone with UID 1000. gdm considers only users with UID 100 system users. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/708911 Title: System users are shown in login screen if they've recently logged in -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 708911] Re: GDM considers only users with uid 500 system users
** Summary changed: - System users are shown in login screen if they've recently logged in + GDM considers only users with uid 500 system users ** Description changed: - Binary package hint: gdm - - Due to the way they start, certain system users turn up in ck-history's - output. Debian Policy defines a system user as someone with UID 1000. - gdm considers only users with UID 100 system users. + Debian Policy defines a system user as someone with UID 1000. gdm + considers only users with UID 100 system users. ** Description changed: Debian Policy defines a system user as someone with UID 1000. gdm - considers only users with UID 100 system users. + considers only users with UID 500 system users. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/708911 Title: GDM considers only users with uid 500 system users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to use CD's from rhythmbox
** Changed in: gst-plugins-base0.10 (Ubuntu) Status: Triaged = Fix Released -- No longer able to use CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
This is now fixed upstream. The relevant cherry picks are: For Rhythmbox: http://git.gnome.org/cgit/rhythmbox/commit/?id=c4931555a29b102d4cba6dcb02123fd50ced9a8d and for gstreamer-plubins-base: http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=6781c4c9c599561a3ca2f964ef9a60b653ee710d http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=901dbc6ab4579398cc1b5f7a80a52a101cfaef54 ** Also affects: gst-plugins-base0.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: gst-plugins-base0.10 (Ubuntu) Status: New = Triaged ** Changed in: rhythmbox (Ubuntu) Status: New = Triaged ** Changed in: gst-plugins-base0.10 (Ubuntu) Importance: Undecided = Medium ** Changed in: rhythmbox (Ubuntu) Importance: Undecided = Medium -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
Marked the bug tasks as medium. I think being able to rip CD's from our main media application is rather important. -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
From #gstreamer: 12:00:57 soren moch: Will that rhythmbox patch from yesterday make it into the upcoming gnome release? 12:08:58 ~moch soren: it made it into the release I put out about half an hour ago, yes ...so we should get the Rhythmbox side fixed with the next GNOME sync. -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
...and the next gstreamer-plugins-base0.10 pre-release will include the rest of the fixes. It's due out early next week, so let's just wait for that to land. -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
It turns out that it's rhythmbox's fault. gstreamer grew a richer URI format for cdda:// URI's, and rhythmbox has been using a different format for a long time, which has happened to work, because gstreamer ignored the extra data in there. ** Package changed: gst-plugins-base0.10 (Ubuntu) = rhythmbox (Ubuntu) -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] [NEW] No longer able to rip CD's from rhythmbox
Public bug reported: After dist-upgrading this morning, I could no longer rip CD's. When I click the button to rip the CD, I get a pop-up telling me that it's Unable to locate encoding profile for mime-type . I blame this source package, because downgrading its binaries to the ones from 0.10.24-2 makes it work again. In other words, it broke between 0.10.24-2 and 0.10.24.2-2. ProblemType: Bug Architecture: amd64 Date: Wed Sep 16 23:29:52 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: libgstreamer-plugins-base0.10-0 0.10.24.2-2 ProcEnviron: PATH=(custom, user) LANG=da_DK.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.34-generic SourcePackage: gst-plugins-base0.10 Uname: Linux 2.6.31-10-generic x86_64 ** Affects: gst-plugins-base0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-base0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431027] Re: No longer able to rip CD's from rhythmbox
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/31923484/Dependencies.txt -- No longer able to rip CD's from rhythmbox https://bugs.launchpad.net/bugs/431027 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-base0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 412948] [NEW] Screen stuck at suboptimal resolution due to virtual size
Public bug reported: This bug report is based on anectodal evidence gathered when helping someone else get back to his proper resolution on his laptop, but I belive it's accurate. He'd been playing around with the TV-Out port, and now his screen was stuck at a resolution of 1360x768, so it didn't fill the screen (which has a physical resolution of 1440x900). It turned out that his xorg.conf specified a virtual resolution of 2048 by 768, so apparantly XRANDR couldn't offer resolutions with a height of more than 768 pixels. I imagine this happened because he at some point had the laptop and the TV-Out both at 1024x768, side by side, and tried to apply it, at which point this setting would get written to xorg.conf. The core problem here, I think, is that there's no obvious way to revert the setting in xorg.conf, and xrandr doesn't even list the resolutions that exceed the virtual resolution, so gnome-display-properties can't even know that there's a higher resolution that is not being shown. affects ubuntu/gnome-control-center ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Screen stuck at suboptimal resolution due to virtual size https://bugs.launchpad.net/bugs/412948 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 366784] Re: Ubuntu 9.04 - PrintScreen Key does not start gnome-screenshot
** Package changed: ubuntu = gnome-utils (Ubuntu) -- Ubuntu 9.04 - PrintScreen Key does not start gnome-screenshot https://bugs.launchpad.net/bugs/366784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 140918] Re: Adding stuff to autostart is too difficult
It seems the Startup Applications Preferences thing implements option no. 2 exactly, so I think the Ubuntu bug can be closed. However, I'm reluctant to close it since the GNOME bug is still open. Pedro, do you have any idea why that is the case? -- Adding stuff to autostart is too difficult https://bugs.launchpad.net/bugs/140918 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 192599] Re: GDM support for domain choice
** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- GDM support for domain choice https://bugs.launchpad.net/bugs/192599 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 140918] Adding stuff to autostart is too difficult
Public bug reported: Binary package hint: gnome-session Getting stuff added to autostart is much too difficult. First of all, guessing that it's in System-Settings-Sessions is not very obvious. Second of all, actually adding stuff to the list is close to impossible if you're not familiar with the layout of the Linux filesystem. Possible solutions in order of preference: 1) Add it to the context menu in the gnome menu. If a program is set to autostart, make this obvious by putting a tiny emblem of some sort in its menu entry. 2) Add a new (sucks, I know) entry to the system-settings menu called Autostart or something. In there, present the list of stuff that's in the gnome menu and put a checkbox next to each entry to make it start automatically. 3) Keep the tab in the gnome-session-preferences, and replace the current Add dialog with a widget that allows you to select a program from the gnome menu and hide the Add dialog under some sort of Advanced thing. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- Adding stuff to autostart is too difficult https://bugs.launchpad.net/bugs/140918 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120284] Re: video podcasts show as failed downloads
** Changed in: rhythmbox (Ubuntu) Importance: Undecided = Wishlist -- video podcasts show as failed downloads https://bugs.launchpad.net/bugs/120284 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
6.04? Do you mean 6.06 perhaps? Is it properly up-to-date? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 79301] Re: Enable burnproof by default
** Changed in: nautilus (Ubuntu) Sourcepackagename: nautilus = nautilus-cd-burner ** Changed in: nautilus-cd-burner (Ubuntu) Status: Unconfirmed = Confirmed ** Attachment added: Proposed fix http://librarian.launchpad.net/5741793/default_burnproof.diff -- Enable burnproof by default https://launchpad.net/bugs/79301 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 66068] Re: New iPod nano recognized as via raid member
On Tue, Nov 28, 2006 at 10:05:57PM -, anthony baxter wrote: Hm. Looking a bit closer, this may be a different issue. The behaviour I'm seeing is that the ipod is getting mounted, but just as (for instance) /media/sdc2, while my old 15G pre-clickwheel ipod is mounted as /media/ipod (or /media/ipod-1) and then the appropriate signals are sent to banshee and amarok to enable it automatically. I'm looking at the output of lshal, and I can't see how the two differ (I have both plugged in right now). You should file a new bug about this. It sounds like a HAL issue. https://launchpad.net/distros/ubuntu/+source/hal/+filebug Cheers. -- New iPod nano recognized as via raid member https://launchpad.net/bugs/66068 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 66068] Re: New iPod nano recognized as via raid member
On Tue, Nov 28, 2006 at 03:00:41PM -, anthony baxter wrote: Will this also fix the same sort of problem with the new 8G nano? dmesg output: Your dmesg output does not in itself suggest anything wrong. The iPod has two partitions. sdc1 holds the iPod's operating system or firmware while sdc2 is the partition that holds your music. The errors in your dmesg output simply tells that something has tried to mount sdc1 which often means that all the different file system drivers will be tried in sequence. None of the will succeed, hence the errors. However, this does not necessarily mean that you're not experiencing the problem that I was seeing. I just can't tell from the dmesg output. Try running lshal, locate the output block that relates to sdc2. If it says via_raid_member somewhere in that block, you're seeing the same bug. Cheers. -- New iPod nano recognized as via raid member https://launchpad.net/bugs/66068 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 66068] Re: New iPod nano recognized as via raid member
On Sat, Nov 18, 2006 at 01:29:29AM -, Stefano Fabri wrote: Are u sure that this bug doesn't must be assigned to udev? Take a look here, seems that was fixed upstram: http://lists.freedesktop.org/archives/hal/2006-October/006412.html The observant reader will notice that it was actually I and Kay who discussed it on the hal mailing list. :-) Whether it belongs in udev or hal depends on whether we want to fix it in Dapper/Edgy or Feisty. Feisty uses hal 0.5.8.1 which uses libvolume_id, while Edgy and Dapper use 0.5.8 which includes its own copy of libvolume_id. Nonetheless, well spotted and thanks for your input. Cheers. -- New iPod nano recognized as via raid member https://launchpad.net/bugs/66068 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66068] New iPod nano recognized as via raid member
Public bug reported: Due to Apple's interesting way of initializing the storage on their new iPod Nano series, the vfat partition is detected as a Via RAID volume, which clearly is not right.. This in turn means that nothing happens when plugging it in, since gnome-volume-manager won't touch raid members. The attached patch adds an extra checksum check to the detection code and hence fixes the issue. ** Affects: hal (Ubuntu) Importance: Undecided Status: Unconfirmed -- New iPod nano recognized as via raid member https://launchpad.net/bugs/66068 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 66068] Re: New iPod nano recognized as via raid member
** Attachment added: Proposed fix http://librarian.launchpad.net/4838850/via-raid-fix.debdiff -- New iPod nano recognized as via raid member https://launchpad.net/bugs/66068 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)
On Tue, Oct 10, 2006 at 08:39:29PM -, BenjaminOtto wrote: How long will it take for a new binary kernel with this fix being released? It shouldn't be more than a few hours at most. Cheers. -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
On Wed, Oct 04, 2006 at 12:22:51PM -, Scott Robinson wrote: Has this patch been pushed upstream through a bug we can track? Not as such. It's been lying around in the hal code commented out for ages, but has recently been commented back in. Besides, pitti said he'd apply the patch tomorrow, so there's not immediate need to do anything further on this bug. -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63725] Re: NM Loses IPW2200 Wireless Device After Suspend
*** This bug is a duplicate of bug 59981 *** ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- NM Loses IPW2200 Wireless Device After Suspend https://launchpad.net/bugs/63725 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
** Bug 63725 has been marked a duplicate of this bug -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60545] Re: Sporadically mixes up wireless network as wired
*** This bug is a duplicate of bug 59981 *** ** This bug is no longer a duplicate of bug 60162 Network manager sometimes gets the device type wrong ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- Sporadically mixes up wireless network as wired https://launchpad.net/bugs/60545 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60162] Re: Network manager sometimes gets the device type wrong
*** This bug is a duplicate of bug 59981 *** ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- Network manager sometimes gets the device type wrong https://launchpad.net/bugs/60162 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
Jacob: So... You still have the problem? -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
** Bug 60545 has been marked a duplicate of this bug ** Bug 60162 has been marked a duplicate of this bug ** Bug 61652 has been marked a duplicate of this bug ** Bug 57501 has been marked a duplicate of this bug -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 61652] Re: (Edgy) NetworkManager gets confused if suspend and wakeup swap network interface names
*** This bug is a duplicate of bug 59981 *** ** This bug is no longer a duplicate of bug 57501 After resume, thinks my wireless network is wired ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- (Edgy) NetworkManager gets confused if suspend and wakeup swap network interface names https://launchpad.net/bugs/61652 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57501] Re: After resume, thinks my wireless network is wired
*** This bug is a duplicate of bug 59981 *** ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
On Fri, Sep 29, 2006 at 08:25:40PM -, Jeff Fortin wrote: Just to be sure, is this patch already in the repository packages, or just in this bug report? Just in this bug report so far. So please be patient. Cheers. -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
On Wed, Sep 27, 2006 at 06:21:18PM -, Jacob Emcken wrote: Should this patch totally remove the problem, or can it theoretically still happen? I observed the same behavior today but I just updated a lot of packages without rebooting/relogging, You have to restart hal before the new package does its thing.. Did you do that? -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
Just FYI: It indeed WAS a race condition. On suspend, most network drivers are unloaded, and are then reloaded on resume. When loading the module, hal is notified of the presence of a new device and quickly add it to it's database. If it's a network interface, it checks /proc/net/wireless to see if the interface in question is mentioned there, and if so, it's marked as being a wifi interface. Apparantly, hal manages to check the file before the device is added to it, and hence it's detected as a non-wifi interface. This new detection code checks for the presence of /sys/class/net/ifname/wireless directory, which seems to be a more robust mechanism for detecting this. Enjoy ** Changed in: network-manager (Ubuntu) Sourcepackagename: network-manager = hal ** Bug 55809 has been marked a duplicate of this bug -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 55809] Re: HAL changes wireless interface (net.80211) to wired (net.80203) in info.category after suspend
*** This bug is a duplicate of bug 59981 *** Marked as duplicate of 59981. In the comments for 59981 there are links to packages for testing a patch which is basically identical to the one attached to this bug report. :-) ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- HAL changes wireless interface (net.80211) to wired (net.80203) in info.category after suspend https://launchpad.net/bugs/55809 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59981] Re: suspend makes network-manager say eth1 is a wired device
** Attachment added: fix typo in changelog http://librarian.launchpad.net/4441289/fix_wifi_detection.diff -- suspend makes network-manager say eth1 is a wired device https://launchpad.net/bugs/59981 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: [Bug 8125] Re: username for smb printer is not shown on printer properties
On Tue, Aug 29, 2006 at 01:16:01AM -, Rocco Stanzione wrote: This bug was reported almost two years ago. Is it still an issue? Yes, it is. For security reasons, CUPS doesn't include the username and password in the info it sends back to a client (in this case gnome-cups-manager). There are two solutions to the problem: 1. Change the GUI so that the user doesn't expect the info to be there. 2. Make CUPS just send the username (and still leave out the password) and just put gibberish in the password field. One of the patches attached to this bug makes CUPS send the username, so it's a pretty easy fix, but clearly no. 1 is the safer choice. However, as I've pointed out previously, there's a good chance we'll be ditching gnome-cups-manager in Edgy in favour of some other tool. -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: [Bug 39484] Re: cups smb printing backend no longer works
On Tue, Jul 04, 2006 at 11:39:50PM -, HarveyB wrote: Can it be confirmed if this bug is still being worked on? To the best of our knowlegde it had been fixed. I have seen the Fix released but I am still having the exact problem with my Dapper 6.06 install. It occured when I did my distro update from 5.10 and I have tried a complete default install as well as adding the printer from our NT domain after a full update of 6.06. The printers connection only lasts until cupsys is restarted, then the user/password info gets dropped and the printer goes to Paused. This sounds like a different issue. The issue handled in this bug was smbspool segfaulting so any samba printers effectively were not working. Does the printer in fact work from the time where you configure it until cupsys is restarted? How do you determine that the user/password info gets dropped? Cheers, Søren -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: [Bug 8125] Re: username for smb printer is not shown on printer properties
On Tue, Jun 27, 2006 at 09:02:08PM -, Kurt Pfeifle wrote: The sanitization of the device URI (not showing username and/or password in log files or other places where device URIs show up for mortal users to see) is in fact a *feature* that was introduced some time ago (it was different before), in order to increase security. I wasn't aware of the chronology of it, but it was quite clear that the removal was intentional. We have three options: 1. Change cups to send the username (not the password of course) 2. Change the UI so that it won't be as surprising that the fields are blank. (e.g. a text telling that it won't be shown but can be used for changing the info) 3. Ditch gnome-cups-manager and go with that new one which I don't remember the name of. As a result of the printing BoF's at the Ubuntu Developer Summit my money is on no. 3. :-) Cheers, Søren. -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: username for smb printer is not shown on printer properties
** Attachment added: Expose username in DeviceURI http://librarian.launchpad.net/2720762/expose-username-in-device-uri.patch -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: username for smb printer is not shown on printer properties
** Attachment added: Remove the nonsense password http://librarian.launchpad.net/2698834/remove_nonsense_from_password_field.patch -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: username for smb printer is not shown on printer properties
** Bug 42325 has been marked a duplicate of this bug -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 42325] Re: Username not shown in the connection tab of properties of a printer
*** This bug is a duplicate of bug 8125 *** ** This bug has been marked a duplicate of bug 8125 username for smb printer is not shown on printer properties -- Username not shown in the connection tab of properties of a printer https://launchpad.net/bugs/42325 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: username for smb printer is not shown on printer properties
I've located the problem. It stems from cups not sending back the full DeviceURI, but rather a sanitized version (read: with all the authentication stuff removed). I've got a patch on my system that makes cups only remove the password. We need to evaluate whether or not this poses a security risk in any way to send the auth username back to the client. Optimally, returning the username would depend on whether or not the user would be allowed to change it, ie. has some sort of administrative rights. I'll see what I can whip up and whether we consider it safe for inclusion in the release. -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 8125] Re: username for smb printer is not shown on printer properties
Oh, and I've got a fix for the password thing too. :-) -- username for smb printer is not shown on printer properties https://launchpad.net/bugs/8125 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
Erich: Agreed. If you're experiencing segmentation faults in other parts of Samba, you should file new bugs for that (or see if there's one already open with the same symptoms). -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
I have a pretty good understanding of this issue (well, the issue fixed by my patch). It was introduced by a patch pulled in from CVS. However, that particular patch was flawed and makes smbspool segfault upon startup. The linux2go patch fixes that particular issue. I believe that any remaining segfaults are symptoms of a different issue. I don't have the black belt in bug management and QA, etc., but I think I see your point. However, I think the best - although not strictly by the almighty book of QA procedures - way to go about this is to maybe change the description of this bug to match the issue fixed by my patch. However, you're the expert and I'm really a lot more interested in fixing bugs than managing bugs. :-) -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
